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 6.8-rc3
Date: Sat, 3 Feb 2024 13:50:09 -0800 [thread overview]
Message-ID: <Zb61EW7GkqldLC7b@kroah.com> (raw)
The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-6.8-rc3
for you to fetch changes up to 97830f3c3088638ff90b20dfba2eb4d487bf14d7:
binder: signal epoll threads of self-work (2024-01-31 14:08:28 -0800)
----------------------------------------------------------------
Char/Misc driver fixes for 6.8-rc3
Here are three tiny driver fixes for 6.8-rc3. They include:
- Android binder long-term bug with epoll finally being fixed
- fastrpc driver shutdown bugfix
- open-dice lockdep fix
All of these have been in linux-next this week with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Carlos Llamas (1):
binder: signal epoll threads of self-work
Ekansh Gupta (1):
misc: fastrpc: Mark all sessions as invalid in cb_remove
Will Deacon (1):
misc: open-dice: Fix spurious lockdep warning
drivers/android/binder.c | 10 ++++++++++
drivers/misc/fastrpc.c | 2 +-
drivers/misc/open-dice.c | 2 +-
3 files changed, 12 insertions(+), 2 deletions(-)
next reply other threads:[~2024-02-03 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 21:50 Greg KH [this message]
2024-02-04 7:18 ` [GIT PULL] Char/Misc driver fixes for 6.8-rc3 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=Zb61EW7GkqldLC7b@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