From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Char/Misc driver fixes for 5.13-rc1
Date: Wed, 5 May 2021 09:14:40 +0200 [thread overview]
Message-ID: <YJJF4O/Ztpw5PQbK@kroah.com> (raw)
The following changes since commit 8e3a3249502d8ff92d73d827fb41dd44c5a16f76:
Merge tag 'char-misc-5.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc (2021-04-26 11:03:17 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-5.13-rc1-round2
for you to fetch changes up to 7b1ae248279bea33af9e797a93c35f49601cb8a0:
dyndbg: fix parsing file query without a line-range suffix (2021-04-30 07:43:20 +0200)
----------------------------------------------------------------
Char/Misc fixes for 5.13-rc1
Here are 2 char/misc fixes for 5.13-rc1 to resolve reported issues.
The first is a bugfix for the nitro_enclaves driver that fixed some
important problems. The second was a dyndbg bugfix that resolved some
reported problems in dynamic debugging control.
Both have been in linux-next for a while with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Mathias Krause (1):
nitro_enclaves: Fix stale file descriptors on failed usercopy
Shuo Chen (1):
dyndbg: fix parsing file query without a line-range suffix
drivers/virt/nitro_enclaves/ne_misc_dev.c | 43 ++++++++++++-------------------
lib/dynamic_debug.c | 2 +-
2 files changed, 18 insertions(+), 27 deletions(-)
next reply other threads:[~2021-05-05 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 7:14 Greg KH [this message]
2021-05-05 20:49 ` [GIT PULL] Char/Misc driver fixes for 5.13-rc1 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=YJJF4O/Ztpw5PQbK@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).