From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.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: [PATCH 6.1 0/6] 6.1.58-rc1 review
Date: Thu, 12 Oct 2023 20:00:42 +0200 [thread overview]
Message-ID: <20231012180030.112560642@linuxfoundation.org> (raw)
This is the start of the stable review cycle for the 6.1.58 release.
There are 6 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 Oct 2023 18:00:23 +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.58-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.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 6.1.58-rc1
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
lib/test_meminit: fix off-by-one error in test_pages()
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Revert "NFS: Fix error handling for O_DIRECT write scheduling"
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Revert "NFS: Fix O_DIRECT locking issues"
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Revert "NFS: More O_DIRECT accounting fixes for error paths"
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Revert "NFS: Use the correct commit info in nfs_join_page_group()"
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Revert "NFS: More fixes for nfs_direct_write_reschedule_io()"
-------------
Diffstat:
Makefile | 4 +-
fs/nfs/direct.c | 134 +++++++++++++++--------------------------------
fs/nfs/write.c | 23 ++++----
include/linux/nfs_page.h | 4 +-
lib/test_meminit.c | 2 +-
5 files changed, 56 insertions(+), 111 deletions(-)
next reply other threads:[~2023-10-12 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 18:00 Greg Kroah-Hartman [this message]
2023-10-12 18:00 ` [PATCH 6.1 6/6] lib/test_meminit: fix off-by-one error in test_pages() Greg Kroah-Hartman
2023-10-12 18:43 ` [PATCH 6.1 0/6] 6.1.58-rc1 review Florian Fainelli
2023-10-12 20:12 ` Pavel Machek
2023-10-13 2:33 ` Guenter Roeck
2023-10-13 5:31 ` Bagas Sanjaya
2023-10-13 12:15 ` Takeshi Ogasawara
2023-10-13 13:10 ` Ron Economos
2023-10-13 13:15 ` Ricardo B. Marliere
2023-10-13 16:53 ` 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=20231012180030.112560642@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.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