From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: [GIT PULL] Staging driver changes for 5.17-rc4
Date: Sat, 12 Feb 2022 11:31:29 +0100 [thread overview]
Message-ID: <YgeMgTqMg82ZC7hA@kroah.com> (raw)
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-5.17-rc4
for you to fetch changes up to 426aca16e903b387a0b0001d62207a745c67cfd3:
staging: fbtft: Fix error path in fbtft_driver_module_init() (2022-01-25 16:36:49 +0100)
----------------------------------------------------------------
Staging driver fixes for 5.17-rc4
Here are 2 staging driver fixes for 5.17-rc4. These are:
- fbtft error path fix
- vc04_services rcu dereference fix
Both of these have been in linux-next for a while with no reported
issues
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Padmanabha Srinivasaiah (1):
staging: vc04_services: Fix RCU dereference check
Uwe Kleine-König (1):
staging: fbtft: Fix error path in fbtft_driver_module_init()
drivers/staging/fbtft/fbtft.h | 5 ++++-
.../vc04_services/interface/vchiq_arm/vchiq_arm.c | 20 ++++++++++++++++++--
2 files changed, 22 insertions(+), 3 deletions(-)
next reply other threads:[~2022-02-12 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 10:31 Greg KH [this message]
2022-02-12 18:23 ` [GIT PULL] Staging driver changes for 5.17-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=YgeMgTqMg82ZC7hA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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