public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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.10.128
Date: Sat,  2 Jul 2022 16:57:33 +0200	[thread overview]
Message-ID: <165677385313453@kroah.com> (raw)

I'm announcing the release of the 5.10.128 kernel.

All users of the 5.10 kernel series must upgrade.

The updated 5.10.y git tree can be found at:
	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.10.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

------------

 MAINTAINERS                                |    3 ++-
 Makefile                                   |    2 +-
 arch/powerpc/include/asm/ftrace.h          |    4 +++-
 arch/powerpc/kernel/trace/ftrace.c         |   15 ++++++++++++---
 arch/powerpc/mm/mem.c                      |    2 ++
 drivers/gpu/drm/drm_crtc_helper_internal.h |   10 ----------
 drivers/gpu/drm/drm_fb_helper.c            |   21 ---------------------
 drivers/gpu/drm/drm_kms_helper_common.c    |   25 ++++++++++++-------------
 drivers/md/bcache/btree.c                  |    1 +
 drivers/md/bcache/writeback.c              |    1 +
 drivers/net/ethernet/mscc/ocelot.c         |    8 ++++++--
 fs/xfs/libxfs/xfs_attr.c                   |   13 +++++--------
 fs/xfs/xfs_aops.c                          |   15 ++++++++++++---
 fs/xfs/xfs_buf_item_recover.c              |    2 +-
 fs/xfs/xfs_extfree_item.c                  |    6 +++---
 fs/xfs/xfs_super.c                         |   14 +++++++++++---
 kernel/time/tick-sched.c                   |    1 -
 17 files changed, 72 insertions(+), 71 deletions(-)

Amir Goldstein (1):
      MAINTAINERS: add Amir as xfs maintainer for 5.10.y

Brian Foster (1):
      xfs: punch out data fork delalloc blocks on COW writeback failure

Christoph Hellwig (1):
      drm: remove drm_fb_helper_modinit

Coly Li (1):
      bcache: memset on stack variables in bch_btree_check() and bch_sectors_dirty_init()

Darrick J. Wong (1):
      xfs: remove all COW fork extents when remounting readonly

Dave Chinner (1):
      xfs: check sb_meta_uuid for dabuf buffer recovery

Greg Kroah-Hartman (1):
      Linux 5.10.128

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

Rustam Kovhaev (1):
      xfs: use kmem_cache_free() for kmem_cache objects

Vladimir Oltean (1):
      net: mscc: ocelot: allow unregistered IP multicast flooding

Yang Xu (1):
      xfs: Fix the free logic of state in xfs_attr_node_hasname


             reply	other threads:[~2022-07-02 14:57 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.10.128 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=165677385313453@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