mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, maz@kernel.org,
	andy.shevchenko@gmail.com, brgl@bgdev.pl, wangyouwan@126.com,
	jani.nikula@intel.com, rf@opensource.cirrus.com,
	ilpo.jarvinen@linux.intel.com, dan.carpenter@linaro.org
Subject: Re: [PATCH 5.10 000/187] 5.10.202-rc3 review
Date: Mon, 27 Nov 2023 22:25:46 +0100	[thread overview]
Message-ID: <ZWUJWhOkbHlwC2YB@duo.ucw.cz> (raw)
In-Reply-To: <20231126154335.643804657@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]

Hi!

> This is the start of the stable review cycle for the 5.10.202 release.
> There are 187 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.

> Marc Zyngier <maz@kernel.org>
>     gpio: Don't fiddle with irqchips marked as immutable

This is attempt to move people to new API, which will cause warning
for existing users. "chip_warn(gc, "not an immutable chip, please
consider fixing it!\n");". It is marked as dependency of another
patch, but I'm not sure we should be doing this in stable.

> youwan Wang <wangyouwan@126.com>
>     Bluetooth: btusb: Add date->evt_skb is NULL check

Could someone double check this? If we hit the null check, we'll be
returning success, but it sounds like an error case.

> Jani Nikula <jani.nikula@intel.com>
>     drm/msm/dp: skip validity check for DP CTS EDID checksum

This is preparation for future cleanup, do we need it?

> Richard Fitzgerald <rf@opensource.cirrus.com>
>     ASoC: soc-card: Add storage for PCI SSID

This adds infrastructure for white/blacklisting, but I don't see an
user of that in 5.10 (or 6.1).

> Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
>     media: cobalt: Use FIELD_GET() to extract Link Width

Cleanup, but not a bugfix.

> Dan Carpenter <dan.carpenter@linaro.org>
>     SUNRPC: Add an IS_ERR() check back to where it was

According to changelog, this is only needed with commit 25cf32ad5dba
("SUNRPC: Handle allocation failure in rpc_new_task()") in tree, and
we don't have that in 5.10.

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 --]

  parent reply	other threads:[~2023-11-27 21:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26 15:46 Greg Kroah-Hartman
2023-11-26 16:22 ` Guenter Roeck
2023-11-27 11:45   ` [PATCH 5.10] interconnect: qcom: Add support for mask-based BCMs djakov
2023-11-27 12:40     ` Greg KH
2023-11-26 18:23 ` [PATCH 5.10 000/187] 5.10.202-rc3 review Guenter Roeck
2023-11-27 12:40   ` Greg Kroah-Hartman
2023-11-27  3:51 ` Florian Fainelli
2023-11-27 21:25 ` Pavel Machek [this message]
2023-11-28  6:56   ` Dominique Martinet
2023-11-28 20:43     ` Pavel Machek
2023-11-28 10:42   ` Richard Fitzgerald
2023-11-28 20:40     ` Pavel Machek
2023-11-29 11:35       ` Richard Fitzgerald
2023-11-27 23:27 ` Jon Hunter
2023-11-27 23:37   ` Jon Hunter
2023-11-28  9:42     ` Greg Kroah-Hartman
2023-11-28  2:52 ` Guenter Roeck
2023-11-28  9:30 ` Naresh Kamboju

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=ZWUJWhOkbHlwC2YB@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=conor@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jani.nikula@intel.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=maz@kernel.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=rf@opensource.cirrus.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wangyouwan@126.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

all inboxes | Powered by JetHome®