Sparclinux Archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: sparclinux@vger.kernel.org, linux-kbuild@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org,  Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 1/3] sparc: vdso: clean up build artifacts in arch/sparc/vdso/
Date: Sun, 10 Dec 2023 15:35:41 +0900	[thread overview]
Message-ID: <CAK7LNAQ5E2T0oitxniLhCAjf4e7QRPfyVpV8SU5P60_j1oF=uA@mail.gmail.com> (raw)
In-Reply-To: <20231203191947.GA147536@ravnborg.org>

On Mon, Dec 4, 2023 at 4:21 AM Sam Ravnborg <sam@ravnborg.org> wrote:
>
> Hi Masahiro.
>
> On Sun, Dec 03, 2023 at 07:14:16PM +0900, Masahiro Yamada wrote:
> > Currently, vdso-image-*.c, vdso*.so, vdso*.so.dbg are not cleaned
> > because 'make clean' does not include include/config/auto.conf,
> > resulting in $(vdso_img-y) being empty.
> >
> > Add the build artifacts to 'targets' unconditionally.
> >
> > Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
>
> Nice small fix/clean-ups.
>
> This and the following two patches are:
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
>
> > ---
> >


Series, applied to linux-kbuild.


-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2023-12-10  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 10:14 [PATCH 1/3] sparc: vdso: clean up build artifacts in arch/sparc/vdso/ Masahiro Yamada
2023-12-03 10:14 ` [PATCH 2/3] sparc: vdso: simplify obj-y addition Masahiro Yamada
2023-12-03 10:14 ` [PATCH 3/3] sparc: vdso: use $(addprefix ) instead of $(foreach ) Masahiro Yamada
2023-12-03 19:19 ` [PATCH 1/3] sparc: vdso: clean up build artifacts in arch/sparc/vdso/ Sam Ravnborg
2023-12-10  6:35   ` Masahiro Yamada [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK7LNAQ5E2T0oitxniLhCAjf4e7QRPfyVpV8SU5P60_j1oF=uA@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sparclinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).