public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, 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: Tue, 17 Dec 2024 10:48:01 +0100	[thread overview]
Message-ID: <2024121753-ransack-monstrous-712b@gregkh> (raw)
In-Reply-To: <68b0559e-47e8-4756-b3de-67d59242756e@roeck-us.net>

On Sun, Dec 15, 2024 at 07:15:24AM -0800, Guenter Roeck wrote:
> On 12/12/24 06:55, Greg Kroah-Hartman wrote:
> > 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.
> > 
> 
> Build results:
> 	total: 156 pass: 147 fail: 9
> Failed builds:
> 	m68k:allnoconfig
> 	m68k:tinyconfig
> 	m68k_nommu:m5272c3_defconfig
> 	m68k_nommu:m5307c3_defconfig
> 	m68k_nommu:m5249evb_defconfig
> 	m68k_nommu:m5407c3_defconfig
> 	m68k_nommu:m5475evb_defconfig
> 	mips:ar7_defconfig
> 	nds32:allmodconfig
> Qemu test results:
> 	total: 480 pass: 479 fail: 1
> Failed tests:
> 	m68k:mcf5208evb:m5208:m5208evb_defconfig:initrd
> 
> Some details below. Reverting
> 
> ef1db3d1d2bf clocksource/drivers:sp804: Make user selectable
> d08932bb6e38 clkdev: remove CONFIG_CLKDEV_LOOKUP
> 
> fixes the problem for m68k:tinyconfig and m68k:m5272c3_defconfig. I didn't check
> if it fixes the other failures, or if the revert affects anything else.

Now dropped, thanks.

greg k-h

      reply	other threads:[~2024-12-17  9:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 14:55 [PATCH 5.10 000/459] 5.10.231-rc1 review 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
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 [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=2024121753-ransack-monstrous-712b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --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