From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
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,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org,
dmitry.torokhov@gmail.com, mmyangfl@gmail.com,
schnelle@linux.ibm.com, g@b4.vu
Subject: Re: [PATCH 6.1 000/141] 6.1.88-rc1 review
Date: Fri, 26 Apr 2024 12:44:21 +0200 [thread overview]
Message-ID: <ZiuFhTU4fPezFe1M@duo.ucw.cz> (raw)
In-Reply-To: <20240423213853.356988651@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
Hi!
> This is the start of the stable review cycle for the 6.1.88 release.
> There are 141 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.
> Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ARM: OMAP2+: pdata-quirks: stop including wl12xx.h
>
> Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ARM: omap2: n8x0: stop instantiating codec platform data
Cleanups. This code is so old it should not really be touched in stable.
> David Yang <mmyangfl@gmail.com>
> HID: kye: Sort kye devices
I guess this is some kind of preparation for something we don't have
in 6.1?
> Niklas Schnelle <schnelle@linux.ibm.com>
> PCI: Make quirk using inw() depend on HAS_IOPORT
This is preparation for patches we won't take to 6.1.
> Niklas Schnelle <schnelle@linux.ibm.com>
> usb: pci-quirks: group AMD specific quirk code together
This is preparation for patches we won't take to 6.1.
> Geoffrey D. Bennett <g@b4.vu>
> ALSA: scarlett2: Rename scarlett_gen2 to scarlett2
Big rename, and it comes after relevant patches, so unneeded.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2024-04-26 10:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 21:37 Greg Kroah-Hartman
2024-04-23 23:00 ` SeongJae Park
2024-04-24 7:21 ` Pavel Machek
2024-04-24 8:23 ` Naresh Kamboju
2024-04-28 12:32 ` Vitaly Chikunov
2024-04-28 16:24 ` Guenter Roeck
2024-04-29 10:21 ` Greg Kroah-Hartman
2024-04-24 8:26 ` Ron Economos
2024-04-24 16:26 ` Florian Fainelli
2024-04-25 9:02 ` Jon Hunter
2024-04-25 9:03 ` Yann Sionneau
2024-04-25 19:27 ` Mateusz Jończyk
2024-04-25 20:08 ` Shreeya Patel
2024-04-26 2:21 ` Mark Brown
2024-04-26 10:44 ` Pavel Machek [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=ZiuFhTU4fPezFe1M@duo.ucw.cz \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=g@b4.vu \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=mmyangfl@gmail.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=rwarsow@gmx.de \
--cc=schnelle@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®