public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: Rename tst-audit26 to tst-audit28
Date: Fri, 8 Jul 2022 13:32:01 +0100	[thread overview]
Message-ID: <YsgjwUge7JV+/FJy@arm.com> (raw)
In-Reply-To: <87bktzq12t.fsf@oldenburg.str.redhat.com>

The 07/08/2022 13:46, Florian Weimer via Libc-alpha wrote:
> tst-audit26 and tst-audit27 are already used by aarch64.
> 
> Tested on aarch64-linux-gnu, i686-linux-gnu, x86_64-linux-gnu.  I think
> this change is sufficient because the next architecture-independent test
> will probably be called tst-audit29, so it is unlikely that the same
> name conflict will be introduced.

this patch looks good.

may be we should name target tests differently going forward
(like tst-aarch64-auditN) that avoids collision.

Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>

      reply	other threads:[~2022-07-08 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 11:46 Florian Weimer
2022-07-08 12:32 ` Szabolcs Nagy [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=YsgjwUge7JV+/FJy@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).