[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YvsocKly+n9S4CsB@kroah.com>
Date: Tue, 16 Aug 2022 07:17:36 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
slade@...dewatkins.com
Subject: Re: [PATCH 5.19 0000/1157] 5.19.2-rc1 review
On Mon, Aug 15, 2022 at 09:09:16PM -0400, Steven Rostedt wrote:
> On Mon, Aug 15, 2022 at 07:49:16PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.19.2 release.
> > There are 1157 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
>
> Hi Greg,
>
> Perhaps its time that you just send a single email to LKML pointing where to
> find the stable releases. These patch bombs are bringing vger down to its
> knees, and causing delays in people's workflows. This doesn't just affect
> LKML, but all other vger mailing lists. Probably because LKML has the biggest
> subscriber base that patch bombs to it can slow everything else down.
>
> I sent 3 patches to the linux-trace-devel list almost 4 hours ago, and they
> still haven't shown up. I was going to point people to it tonight but it's now
> going to have to wait till tomorrow.
Email is async, sometimes it takes longer than others to recieve
messages.
My "patch bombs" get sent out slow to the mail servers, there is work to
fix up vger and move it over to the LF-managed infrastructure, perhaps
work with the vger admins to help that effort out?
> I really do not think LKML needs to see all 1157 patches that are being
> backported. There's other places to send them that will not be as disruptive.
And where would that be?
Getting the patches out for review is good, and necessary. Patches
should never be considered "noise" as it is what we are doing here. If
we have infrastructure issues handling these messages, we should work to
resolve them as really, 3000 emails should not be a lot to manage,
unless you are being throttled by your email provider?
thanks,
greg k-h
Powered by blists - more mailing lists