All of lore.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 5.13-rc4
Date: Sat, 29 May 2021 16:27:24 +0200	[thread overview]
Message-ID: <YLJPTFZ8aIx7Mu20@kroah.com> (raw)

The following changes since commit d07f6ca923ea0927a1024dfccafc5b53b61cfecc:

  Linux 5.13-rc2 (2021-05-16 15:27:44 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-5.13-rc4

for you to fetch changes up to 0c8713153fbf7ba4e45172e139d501c86006dc03:

  drivers: base: Reduce device link removal code duplication (2021-05-21 22:12:14 +0200)

----------------------------------------------------------------
Driver core fixes for 5.13-rc4

Here are 3 small driver core / debugfs fixes for 5.13-rc4:
  - debugfs fix for incorrect "lockdown" mode for selinux accesses
  - 2 device link changes, one bugfix and one cleanup

All of these have been in linux-next for over a week with no reported
problems.

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

----------------------------------------------------------------
Ondrej Mosnacek (1):
      debugfs: fix security_locked_down() call for SELinux

Rafael J. Wysocki (2):
      drivers: base: Fix device link removal
      drivers: base: Reduce device link removal code duplication

 drivers/base/core.c    | 68 ++++++++++++++++++++++++++------------------------
 fs/debugfs/inode.c     |  9 ++++---
 include/linux/device.h |  6 ++---
 3 files changed, 44 insertions(+), 39 deletions(-)

             reply	other threads:[~2021-05-29 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29 14:27 Greg KH [this message]
2021-05-29 16:49 ` [GIT PULL] Driver core fixes for 5.13-rc4 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=YLJPTFZ8aIx7Mu20@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.