From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Linux 5.18.9
Date: Sat, 2 Jul 2022 16:57:43 +0200 [thread overview]
Message-ID: <1656773864192163@kroah.com> (raw)
I'm announcing the release of the 5.18.9 kernel.
All users of the 5.18 kernel series must upgrade.
The updated 5.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.18.y
and can be browsed at the normal kernel.org git web browser:
https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
thanks,
greg k-h
------------
Makefile | 2 -
arch/powerpc/include/asm/ftrace.h | 4 +-
arch/powerpc/kernel/trace/ftrace.c | 15 +++++++--
arch/powerpc/mm/mem.c | 2 +
drivers/clocksource/Kconfig | 2 -
drivers/clocksource/timer-ixp4xx.c | 25 ----------------
drivers/md/bcache/btree.c | 1
drivers/md/bcache/writeback.c | 1
drivers/net/ethernet/huawei/hinic/hinic_devlink.c | 4 --
fs/io_uring.c | 34 +++++++++++-----------
include/linux/platform_data/timer-ixp4xx.h | 11 -------
kernel/time/tick-sched.c | 1
12 files changed, 40 insertions(+), 62 deletions(-)
Coly Li (1):
bcache: memset on stack variables in bch_btree_check() and bch_sectors_dirty_init()
Greg Kroah-Hartman (1):
Linux 5.18.9
Kees Cook (1):
hinic: Replace memcpy() with direct assignment
Linus Walleij (1):
clocksource/drivers/ixp4xx: Drop boardfile probe path
Masahiro Yamada (1):
tick/nohz: unexport __init-annotated tick_nohz_full_setup()
Naveen N. Rao (1):
powerpc/ftrace: Remove ftrace init tramp once kernel init is complete
Pavel Begunkov (1):
io_uring: fix not locked access to fixed buf table
next reply other threads:[~2022-07-02 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 14:57 Greg Kroah-Hartman [this message]
2022-07-02 14:57 ` Linux 5.18.9 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=1656773864192163@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--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