From: Joel Fernandes <joel@joelfernandes.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
Subject: Re: [PATCH 6.1 0/4] 6.1.49-rc1 review
Date: Sat, 26 Aug 2023 20:57:03 +0000 [thread overview]
Message-ID: <20230826205703.GA2311600@google.com> (raw)
In-Reply-To: <20230826154625.450325166@linuxfoundation.org>
On Sat, Aug 26, 2023 at 05:47:56PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.49 release.
> There are 4 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 Mon, 28 Aug 2023 15:46:14 +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.1.49-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.1.y
> and the diffstat can be found below.
Tested-by: Joel Fernandes (Google) <joel@joelfernandes.org>
thanks,
- Joel
>
> thanks,
>
> greg k-h
>
> -------------
> Pseudo-Shortlog of commits:
>
> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Linux 6.1.49-rc1
>
> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Revert "f2fs: fix to do sanity check on direct node in truncate_dnode()"
>
> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Revert "f2fs: fix to set flush_merge opt and show noflush_merge"
>
> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Revert "f2fs: don't reset unchangable mount option in f2fs_remount()"
>
> Peter Zijlstra <peterz@infradead.org>
> objtool/x86: Fix SRSO mess
>
>
> -------------
>
> Diffstat:
>
> Makefile | 4 ++--
> fs/f2fs/f2fs.h | 1 +
> fs/f2fs/file.c | 5 +++++
> fs/f2fs/node.c | 14 ++----------
> fs/f2fs/super.c | 43 ++++++++++++------------------------
> include/linux/f2fs_fs.h | 1 -
> tools/objtool/arch/x86/decode.c | 11 +++++----
> tools/objtool/check.c | 22 +++++++++++++++++-
> tools/objtool/include/objtool/arch.h | 1 +
> tools/objtool/include/objtool/elf.h | 1 +
> 10 files changed, 54 insertions(+), 49 deletions(-)
>
>
next prev parent reply other threads:[~2023-08-26 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 15:47 [PATCH 6.1 0/4] 6.1.49-rc1 review Greg Kroah-Hartman
2023-08-26 20:57 ` Joel Fernandes [this message]
2023-08-27 1:33 ` Takeshi Ogasawara
2023-08-27 8:44 ` Sudip Mukherjee (Codethink)
2023-08-27 10:49 ` Bagas Sanjaya
2023-08-27 11:20 ` Guenter Roeck
2023-08-28 8:03 ` 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=20230826205703.GA2311600@google.com \
--to=joel@joelfernandes.org \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--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=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