From: Florian Weimer <fweimer@redhat.com>
To: Tulio Magno Quites Machado Filho via Libc-alpha
<libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] powerpc64: Workaround sigtramp vdso return call
Date: Thu, 11 Feb 2021 22:55:54 +0100 [thread overview]
Message-ID: <87lfbumfpx.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87czxp575w.fsf@linux.ibm.com> (Tulio Magno Quites Machado Filho via Libc-alpha's message of "Thu, 28 Jan 2021 13:59:39 -0300")
* Tulio Magno Quites Machado Filho via Libc-alpha:
>> LGTM, it is ok for 2.33.
>>
>> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
>
> Pushed as 5ee506ed35a2c9184bcb1fb5e79b6cceb9bb0dd1
Why isn't this handled as a kernel regression?
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2021-02-11 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 19:23 Raoni Fassina Firmino
2021-01-27 19:33 ` Adhemerval Zanella
2021-01-28 16:59 ` Tulio Magno Quites Machado Filho
2021-02-11 21:55 ` Florian Weimer [this message]
2021-02-12 2:14 ` Adhemerval Zanella
2021-02-15 17:51 ` Raoni Fassina Firmino
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=87lfbumfpx.fsf@oldenburg.str.redhat.com \
--to=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).