public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	 Libc-stable Mailing List <libc-stable@sourceware.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Replace tst-audit24bmod2.so with tst-audit24bmod2
Date: Tue, 22 Feb 2022 06:56:15 -0800	[thread overview]
Message-ID: <CAMe9rOpTnkCSvS0qpnWbJ4RyC-9H9j-QwAWobo4BCUyE7oMRdA@mail.gmail.com> (raw)
In-Reply-To: <6e398ab6-4197-894f-7ab6-8dd846818665@linaro.org>

On Mon, Feb 7, 2022 at 3:03 AM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
>
>
>
> On 06/02/2022 16:17, H.J. Lu wrote:
> >> @@ -919,7 +942,8 @@ extra-test-objs += $(addsuffix .os,$(strip $(modules-names)))
> >>
> >>  # filtmod1.so, tst-big-note-lib.so, tst-ro-dynamic-mod.so have special
> >>  # rules.
> >> -modules-names-nobuild := filtmod1 tst-big-note-lib tst-ro-dynamic-mod
> >> +modules-names-nobuild := filtmod1 tst-big-note-lib tst-ro-dynamic-mod \
> >> +                        tst-audit24bmod1 tst-audit24bmod2.so
> >
> >              ^^^^ Not needed.
> >
> > I got
> >
> > make[2]: Entering directory '/export/gnu/import/git/gitlab/x86-glibc/elf'
> > Makefile:2201: warning: overriding recipe for target
> > '/export/build/gnu/tools-build/glibc-gitlab/build-x86_64-linux/elf/tst-audit24bmod2.so'
> > ../Makerules:765: warning: ignoring old recipe for target
> > '/export/build/gnu/tools-build/glibc-gitlab/build-x86_64-linux/elf/tst-audit24bmod2.so'
> >
> > I am testing the enclosed patch and will push it if tests pass.
> >
> > H.J.
>
> Thanks, looks obvious enough for me.

I am backporting it to 2.35 branch.

-- 
H.J.

           reply	other threads:[~2022-02-22 14:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <6e398ab6-4197-894f-7ab6-8dd846818665@linaro.org>]

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=CAMe9rOpTnkCSvS0qpnWbJ4RyC-9H9j-QwAWobo4BCUyE7oMRdA@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-stable@sourceware.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).