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: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Staging driver fixes for 5.7-rc5
Date: Fri, 8 May 2020 16:18:07 +0200 [thread overview]
Message-ID: <20200508141807.GA353767@kroah.com> (raw)
The following changes since commit 6a8b55ed4056ea5559ebe4f6a4b247f627870d4c:
Linux 5.7-rc3 (2020-04-26 13:51:02 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-5.7-rc5
for you to fetch changes up to 769acc3656d93aaacada814939743361d284fd87:
staging: gasket: Check the return value of gasket_get_bar_index() (2020-05-05 12:36:05 +0200)
----------------------------------------------------------------
Staging driver fixes for 5.7-rc5
Here are 3 small driver fixes for 5.7-rc5.
Two of these are documentation fixes:
- MAINTAINERS update due to removed driver
- removing Wolfram from the ks7010 driver TODO file
The other patch is a real fix:
- fix gasket driver to proper check the return value of a call
All of these have been in linux-next for a while with no reported
issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Lukas Bulwahn (1):
MAINTAINERS: remove entry after hp100 driver removal
Oscar Carter (1):
staging: gasket: Check the return value of gasket_get_bar_index()
Wolfram Sang (1):
staging: ks7010: remove me from CC list
MAINTAINERS | 5 -----
drivers/staging/gasket/gasket_core.c | 4 ++++
drivers/staging/ks7010/TODO | 1 -
3 files changed, 4 insertions(+), 6 deletions(-)
next reply other threads:[~2020-05-08 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 14:18 Greg KH [this message]
2020-05-08 16:15 ` [GIT PULL] Staging driver fixes for 5.7-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=20200508141807.GA353767@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@vger.kernel.org \
--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