public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Raoni Fassina Firmino <raoni@linux.ibm.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Tulio Magno Quites Machado Filho via Libc-alpha
	<libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] powerpc64: Workaround sigtramp vdso return call
Date: Mon, 15 Feb 2021 14:51:48 -0300	[thread overview]
Message-ID: <20210215175148.z7qnlfpbhgvlw3vf@work-tp> (raw)
In-Reply-To: <87lfbumfpx.fsf@oldenburg.str.redhat.com>

On Thu, Feb 11, 2021 at 10:55:54PM +0100, AL glibc-alpha wrote:
> * 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?

I don't know if you mean a specific workflow to flag this as a
regression in any bugtrack or something like that.  Apart from that IMHO
It is is a regression as I mentioned in some prior email[1] and I
characterized it as such in my kernel patch[2] that was include for the
5.11 release and backported for 5.10.16.  At least no one questioned
this characterization.

o/
Raoni

[1] https://sourceware.org/pipermail/libc-alpha/2021-January/121951.html
[2] https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-February/223585.html

      parent reply	other threads:[~2021-02-15 17:51 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
2021-02-12  2:14       ` Adhemerval Zanella
2021-02-15 17:51       ` Raoni Fassina Firmino [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=20210215175148.z7qnlfpbhgvlw3vf@work-tp \
    --to=raoni@linux.ibm.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).