From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>,
Libc-stable Mailing List <libc-stable@sourceware.org>
Cc: Matheus Castanho <msc@linux.ibm.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Please test: [2.31/2.30] [PATCH] powerpc: Rename argN to _argN in LOADARGS_N [BZ #25902]
Date: Fri, 1 May 2020 16:11:50 -0700 [thread overview]
Message-ID: <CAMe9rOq4o+biT55RubTzkcR9-a+2AGDDKeJmKfeXy3PALb7JTg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOrkBcK810Jnr90XtVvmPru_o_rndQpk=aY+gREfnyGdCA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
On Thu, Apr 30, 2020 at 7:18 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Thu, Apr 30, 2020 at 7:03 PM Tulio Magno Quites Machado Filho
> <tuliom@ascii.art.br> wrote:
> >
> > "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org> writes:
> >
> > > See:
> > >
> > > https://sourceware.org/bugzilla/show_bug.cgi?id=25902
> > >
> > > with a patch. But I can't test it natively.
> >
> > Tested. LGTM.
> >
> > Could you push it, please?
>
> This is I am checking in. I will backport it to 2.30/2.31 branches
> together with
>
> commit ff026950e280bc3e9487b41b460fb31bc5b57721
> Author: H.J. Lu <hjl.tools@gmail.com>
> Date: Thu Apr 30 10:42:43 2020 -0700
>
> Add a C wrapper for prctl [BZ #25896]
>
I need to update both powerpc32/sysdep.h and powerpc64/sysdep.h
on 2.30 and 2.31 branches, instead of just powerpc/sysdep.h. Can
someone please test this patch on 2.30 and 2.31 branches on PPC?
Thanks.
--
H.J.
[-- Attachment #2: 0001-powerpc-Rename-argN-to-_argN-in-LOADARGS_N-BZ-25902.patch --]
[-- Type: application/x-patch, Size: 5975 bytes --]
next prev parent reply other threads:[~2020-05-01 23:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 20:52 [PATCH] Add a C wrapper for prctl [BZ #25896] H.J. Lu
2020-04-30 7:26 ` Florian Weimer
2020-04-30 13:03 ` V2 " H.J. Lu
2020-04-30 13:41 ` Andreas Schwab
2020-04-30 13:43 ` Florian Weimer
2020-04-30 13:50 ` H.J. Lu
2020-04-30 13:51 ` Andreas Schwab
2020-04-30 13:53 ` H.J. Lu
2020-04-30 14:04 ` Andreas Schwab
2020-04-30 15:27 ` V3 " H.J. Lu
2020-04-30 16:53 ` Florian Weimer
2020-04-30 17:20 ` [PATCH] Add a " H.J. Lu
2020-04-30 20:01 ` V3 [PATCH] Add a C " Florian Weimer
2022-11-10 8:33 ` Florian Weimer
2022-11-10 11:49 ` Adhemerval Zanella Netto
2022-11-10 12:03 ` Florian Weimer
2022-11-10 12:25 ` Adhemerval Zanella Netto
2022-11-10 13:17 ` Florian Weimer
2020-04-30 13:54 ` V2 " Florian Weimer
2020-04-30 14:51 ` Adhemerval Zanella
2020-04-30 16:35 ` H.J. Lu
2020-04-30 16:51 ` Florian Weimer
2020-04-30 17:24 ` Adhemerval Zanella
2020-04-30 17:29 ` V4 " H.J. Lu
[not found] ` <c2a821bf-fd2a-0ed9-2ad9-c4bd1231b2a7@linux.ibm.com>
[not found] ` <CAMe9rOq60aAKujxFF=bSyN5yPZVWSa-KWKWXKHpB8uOKu5V-7w@mail.gmail.com>
2020-04-30 22:57 ` Bad LOADARGS_N on PPC H.J. Lu
2020-05-01 2:03 ` Tulio Magno Quites Machado Filho
2020-05-01 2:18 ` [PATCH] powerpc: Rename argN to _argN in LOADARGS_N [BZ #25902] H.J. Lu
2020-05-01 23:11 ` H.J. Lu [this message]
2020-05-04 16:00 ` Please test: [2.31/2.30] " Matheus Castanho
2020-05-04 19:11 ` H.J. Lu
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=CAMe9rOq4o+biT55RubTzkcR9-a+2AGDDKeJmKfeXy3PALb7JTg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@sourceware.org \
--cc=msc@linux.ibm.com \
--cc=tuliom@ascii.art.br \
/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).