linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: axboe@kernel.dk, linux-arm-kernel@lists.infradead.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "arm: add support for TIF_NOTIFY_SIGNAL" has been added to the 5.10-stable tree
Date: Tue, 3 Jan 2023 15:57:48 +0000	[thread overview]
Message-ID: <Y7RQfBUlYeNEbnu1@shell.armlinux.org.uk> (raw)
In-Reply-To: <Y7RP06GTZL030C94@kroah.com>

On Tue, Jan 03, 2023 at 04:54:59PM +0100, Greg KH wrote:
> On Tue, Jan 03, 2023 at 10:37:22AM +0000, Russell King (Oracle) wrote:
> > Hi Greg,
> > 
> > Probably not a good idea to pick this up just yet - there's been a
> > report of a performance regression due to this patch.
> 
> There is?

Why do I get the impression that you think I'm lying? This is not a good
start to the year.

Yes, I'm making it up. It's all in my mind. Carry on as you would. I
don't care anymore about shite stable kernels.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-01-03 17:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03  7:36 Patch "arm: add support for TIF_NOTIFY_SIGNAL" has been added to the 5.10-stable tree gregkh
2023-01-03 10:37 ` Russell King (Oracle)
2023-01-03 14:26   ` Jens Axboe
2023-01-03 15:54   ` Greg KH
2023-01-03 15:57     ` Russell King (Oracle) [this message]
2023-01-03 16:20       ` Greg KH
2023-01-09 17:02         ` Russell King (Oracle)
2023-01-03 15:57     ` Jens Axboe
2023-01-03 16:21       ` Greg KH
2023-01-06 22:33         ` Jens Axboe
2023-01-07 11:03           ` Greg KH

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=Y7RQfBUlYeNEbnu1@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=stable-commits@vger.kernel.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 NNTP newsgroup(s).