linux-kernel - Re: [PATCH 4.14 00/53] 4.14.331-rc2 review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f4a7634-3d34-af29-36ca-6f3439b4ce9@linux.intel.com>
Date:   Tue, 28 Nov 2023 15:10:53 +0200 (EET)
From:   Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To:     Pavel Machek <pavel@...x.de>
cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        stable@...r.kernel.org, patches@...ts.linux.dev,
        LKML <linux-kernel@...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, jonathanh@...dia.com,
        f.fainelli@...il.com, sudipm.mukherjee@...il.com,
        srw@...dewatkins.net, rwarsow@....de, conor@...nel.org,
        allen.lkml@...il.com, alexander.deucher@....com,
        mario.limonciello@....com, zhujun2@...s.chinamobile.com,
        sashal@...nel.org, skhan@...uxfoundation.org, bhelgaas@...gle.com
Subject: Re: [PATCH 4.14 00/53] 4.14.331-rc2 review

On Mon, 27 Nov 2023, Pavel Machek wrote:

> Hi!
> 
> > This is the start of the stable review cycle for the 4.14.331 release.
> > There are 53 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.

> > Ilpo Järvinen <ilpo.jarvinen@...ux.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@...ux.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.


-- 
 i.