From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Sergey Bugaev <bugaevc@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 2/2] x86: Make dl-cache.h and readelflib.c not Linux-specific
Date: Fri, 23 Jun 2023 09:46:32 -0300 [thread overview]
Message-ID: <bc04ab71-ceff-62dc-c678-d9bbbb981659@linaro.org> (raw)
In-Reply-To: <CAN9u=HeqAks8cRLe8dbgKP=3=SuqexNUDsirFyjmn8a9tp1X+w@mail.gmail.com>
On 23/06/23 09:36, Sergey Bugaev wrote:
> Hello,
>
> On Wed, Jun 21, 2023 at 4:28 PM Adhemerval Zanella Netto
> <adhemerval.zanella@linaro.org> wrote:
>> LGTM, thanks.
>>
>> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
>
> Thanks.
>
> So assuming everyone is happy with this patchset now, what is the
> process for getting it pushed? Do I need to ping anyone specific?
> Previously Samuel pushed my patches after reviewing them, but I
> imagine that wouldn't be the case for patches that are not
> Hurd-specific.
>
> (And please also reply to the question about Reviewed-by in the previous patch!)
I will take care of this.
next prev parent reply other threads:[~2023-06-23 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 16:40 [PATCH v3 1/2] elf: Port ldconfig away from stack-allocated paths Sergey Bugaev
2023-06-17 16:40 ` [PATCH v3 2/2] x86: Make dl-cache.h and readelflib.c not Linux-specific Sergey Bugaev
2023-06-21 13:28 ` Adhemerval Zanella Netto
2023-06-23 12:36 ` Sergey Bugaev
2023-06-23 12:46 ` Adhemerval Zanella Netto [this message]
2023-06-26 19:39 ` Joseph Myers
2023-06-26 19:50 ` Adhemerval Zanella Netto
2023-06-26 20:05 ` Sergey Bugaev
2023-06-26 20:09 ` Sergey Bugaev
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=bc04ab71-ceff-62dc-c678-d9bbbb981659@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=bugaevc@gmail.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).