public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Saravana Kannan <saravanak@google.com>
Subject: [GIT PULL] Driver core fixes for 6.4-rc5
Date: Sun, 4 Jun 2023 10:05:05 +0200	[thread overview]
Message-ID: <ZHxFsQHCXZ9Q56uu@kroah.com> (raw)

The following changes since commit 7877cb91f1081754a1487c144d85dc0d2e2e7fc4:

  Linux 6.4-rc4 (2023-05-28 07:49:00 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-6.4-rc5

for you to fetch changes up to c26fabe73330d983c7ce822c6b6ec0879b4da61f:

  drivers: base: cacheinfo: Update cpu_map_populated during CPU Hotplug (2023-05-31 20:36:47 +0100)

----------------------------------------------------------------
Driver core fixes for 6.4-rc5

Here are 2 small driver core cacheinfo fixes for 6.4-rc5 that resolve a
number of reported issues with that file.  These changes have been in
linux-next this past week with no reported problems.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
K Prateek Nayak (2):
      drivers: base: cacheinfo: Fix shared_cpu_map changes in event of CPU hotplug
      drivers: base: cacheinfo: Update cpu_map_populated during CPU Hotplug

 drivers/base/cacheinfo.c | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

             reply	other threads:[~2023-06-04  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04  8:05 Greg KH [this message]
2023-06-04 12:59 ` [GIT PULL] Driver core fixes for 6.4-rc5 pr-tracker-bot

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=ZHxFsQHCXZ9Q56uu@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saravanak@google.com \
    --cc=sfr@canb.auug.org.au \
    --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