public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	LKML <linux-kernel@vger.kernel.org>,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, jonathanh@nvidia.com,
	f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
	allen.lkml@gmail.com, alexander.deucher@amd.com,
	mario.limonciello@amd.com, zhujun2@cmss.chinamobile.com,
	sashal@kernel.org, skhan@linuxfoundation.org,
	bhelgaas@google.com
Subject: Re: [PATCH 4.14 00/53] 4.14.331-rc2 review
Date: Tue, 28 Nov 2023 21:10:03 +0000	[thread overview]
Message-ID: <2023112844-sesame-overdrawn-5853@gregkh> (raw)
In-Reply-To: <ZWZSKgxjSRcA/qUK@duo.ucw.cz>

On Tue, Nov 28, 2023 at 09:48:42PM +0100, Pavel Machek wrote:
> Hi!
> 
> > > > > > Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > > > > >     RDMA/hfi1: Use FIELD_GET() to extract Link Width
> > > > > 
> > > > > This is a good cleanup, but not a bugfix.
> > > > > 
> > > > > > Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > > > > >     atm: iphase: Do PCI error checks on own line
> > > > > 
> > > > > Just a cleanup, not sure why it was picked for stable.
> > > > 
> > > > Just an additional bit of information, there have been quite many cleanups 
> > > > from me which have recently gotten the stable notification for some 
> > > > mysterious reason. When I had tens of them in my inbox and for various 
> > > > kernel versions, I immediately stopped caring to stop it from happening.
> > > > 
> > > > AFAIK, I've not marked those for stable inclusion so I've no idea what
> > > > got them included.
> > > 
> > > Fixes tag can do it. Plus, "AUTOSEL" robot does it randomly, with no
> > > human oversight :-(.
> > 
> > the autosel bot has lots of oversight.
> 
> Can you describe how that oversight works?

There have been many papers and presentations about it, no need for me
to say it all here again...

  reply	other threads:[~2023-11-28 21:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25 16:32 [PATCH 4.14 00/53] 4.14.331-rc2 review Greg Kroah-Hartman
2023-11-25 20:10 ` Pavel Machek
2023-11-26 18:33 ` Guenter Roeck
2023-11-26 20:39   ` Helge Deller
2023-11-27 12:47     ` Greg Kroah-Hartman
2023-11-27  5:47 ` Harshit Mogalapalli
2023-11-27 14:33 ` Naresh Kamboju
2023-11-27 20:51 ` Pavel Machek
2023-11-28 13:10   ` Ilpo Järvinen
2023-11-28 20:39     ` Pavel Machek
2023-11-28 20:43       ` Greg Kroah-Hartman
2023-11-28 20:48         ` Pavel Machek
2023-11-28 21:10           ` Greg Kroah-Hartman [this message]
2023-11-29  9:00             ` Pavel Machek
2023-11-29 17:45               ` Sasha Levin
2023-11-29 11:20       ` Ilpo Järvinen
2023-11-27 23:25 ` Jon Hunter
2023-11-28  2:49 ` Guenter Roeck

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=2023112844-sesame-overdrawn-5853@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.deucher@amd.com \
    --cc=allen.lkml@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mario.limonciello@amd.com \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=zhujun2@cmss.chinamobile.com \
    /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