mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
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, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 5.10 000/459] 5.10.231-rc1 review
Date: Fri, 13 Dec 2024 22:25:52 +0900	[thread overview]
Message-ID: <Z1w14PaRR2d7lyHZ@codewreck.org> (raw)
In-Reply-To: <20241212144253.511169641@linuxfoundation.org>

Greg Kroah-Hartman wrote on Thu, Dec 12, 2024 at 03:55:38PM +0100:
> This is the start of the stable review cycle for the 5.10.231 release.
> There are 459 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.
> 
> Responses should be made by Sat, 14 Dec 2024 14:41:35 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.231-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.

Tested 2146a7485c27 ("Linux 5.10.231-rc1") on:
- arm i.MX6ULL (Armadillo 640)
- arm64 i.MX8MP (Armadillo G4)

No obvious regression in dmesg or basic tests:
Tested-by: Dominique Martinet <dominique.martinet@atmark-techno.com>



> Shengjiu Wang <shengjiu.wang@nxp.com>
>     ASoC: fsl_micfil: fix the naming style for mask definition
>
> Shengjiu Wang <shengjiu.wang@nxp.com>
>     ASoC: fsl_micfil: fix regmap_write_bits usage
> 
> Sascha Hauer <s.hauer@pengutronix.de>
>     ASoC: fsl_micfil: use GENMASK to define register bit fields
> 
> Sascha Hauer <s.hauer@pengutronix.de>
>     ASoC: fsl_micfil: do not define SHIFT/MASK for single bits
> 
> Sascha Hauer <s.hauer@pengutronix.de>
>     ASoC: fsl_micfil: Drop unnecessary register read

Just a note on these, our version (from nxp) of this was full of
conflicts and too much effort to merge for something I cannot test
easily, so I squashed out this part and re-cherry-picked just commits
c808e277bcdf ("ASoC: fsl_micfil: Drop unnecessary register read")
and 06df673d2023 ("ASoC: fsl_micfil: fix regmap_write_bits usage")

The other three commits are marked as a stable dep of 06df673d2023 but
it really is trivial to backport and not worth the risk to me; if you'd
like me to send the minimal backport I used I'll be happy to.

(but, as far as I'm concerned I'm fine as is as well and consider this
closed; just reporting I didn't test this 100% as is. Not that my
automated test actually exercises the micfil code anyway...)


Thanks,
-- 
Dominique Martinet

  parent reply	other threads:[~2024-12-13 13:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 14:55 Greg Kroah-Hartman
2024-12-12 14:59 ` [PATCH 5.10 203/459] m68k: coldfire/device.c: only build FEC when HW macros are defined Greg Kroah-Hartman
2024-12-12 20:07 ` [PATCH 5.10 000/459] 5.10.231-rc1 review Florian Fainelli
2024-12-13 10:03 ` Jon Hunter
2024-12-13 13:17 ` Mark Brown
2024-12-13 13:25 ` Dominique Martinet [this message]
2024-12-13 19:55 ` Pavel Machek
2024-12-14  8:54 ` Muhammad Usama Anjum
2024-12-14  9:04 ` Muhammad Usama Anjum
2024-12-14 11:16 ` Naresh Kamboju
2024-12-15 15:15 ` Guenter Roeck
2024-12-17  9:48   ` Greg Kroah-Hartman

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=Z1w14PaRR2d7lyHZ@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --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 \
    /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®