From: David Sterba <dsterba@suse.cz>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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, hagar@microsoft.com, broonie@kernel.org,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Linux btrfs <linux-btrfs@vger.kernel.org>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH 6.11 000/245] 6.11.7-rc1 review
Date: Wed, 6 Nov 2024 17:07:08 +0100 [thread overview]
Message-ID: <20241106160708.GE31418@suse.cz> (raw)
In-Reply-To: <CA+G9fYtjpUJFFV=FdqvW+5K+JL5ZYN4sPfVDjQovqzd7cib39w@mail.gmail.com>
On Wed, Nov 06, 2024 at 03:12:46PM +0000, Naresh Kamboju wrote:
> On Wed, 6 Nov 2024 at 12:26, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.11.7 release.
> > There are 245 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 Fri, 08 Nov 2024 12:02:47 +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/v6.x/stable-review/patch-6.11.7-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-6.11.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> The mips gcc-12 allmodconfig build failed on the Linux stable-rc
> linux-6.11.y branch.
>
>
> First seen on Linux stable-rc v6.11.4-642-g0e21c72fc970
>
> Good: v6.11.4-397-g4ccf0b49d5b6
> Bad: v6.11.4-642-g0e21c72fc970
>
> mips:
> build:
> * gcc-12-allmodconfig
>
> Build errors:
> -------------
> ERROR: modpost: "__cmpxchg_small" [fs/btrfs/btrfs.ko] undefined!
The patch "btrfs: fix error propagation of split bios" needs
90a88784cdb7 ("MIPS: export __cmpxchg_small()")
next prev parent reply other threads:[~2024-11-06 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 12:00 [PATCH 6.11 000/245] 6.11.7-rc1 review Greg Kroah-Hartman
2024-11-06 13:47 ` Luna Jernberg
2024-11-06 15:12 ` Naresh Kamboju
2024-11-06 16:07 ` David Sterba [this message]
2024-11-07 6:33 ` Greg Kroah-Hartman
2024-11-06 16:55 ` SeongJae Park
2024-11-07 2:26 ` Shuah Khan
-- strict thread matches above, loose matches on Subject: below --
2024-11-06 15:24 Ronald Warsow
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=20241106160708.GE31418@suse.cz \
--to=dsterba@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=clm@fb.com \
--cc=conor@kernel.org \
--cc=dsterba@suse.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hagar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@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