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,
linux-staging@lists.linux.dev
Subject: [GIT PULL] Staging driver fixes for 5.13-rc6
Date: Sat, 12 Jun 2021 17:54:31 +0200 [thread overview]
Message-ID: <YMTYtya0Sn/JVtz2@kroah.com> (raw)
The following changes since commit 8124c8a6b35386f73523d27eacb71b5364a68c4c:
Linux 5.13-rc4 (2021-05-30 11:58:25 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-5.13-rc6
for you to fetch changes up to e9de1ecadeab5fbffd873b9110e969c869554a56:
staging: ralink-gdma: Remove incorrect author information (2021-06-09 12:07:52 +0200)
----------------------------------------------------------------
Staging driver fixes for 5.13-rc6
Here are two tiny staging driver fixes for 5.13-rc6
- ralink-gdma driver authorship information fixed up
- rtl8723bs driver fix for reported regression
Both have been in linux-next for a while with no reported problems.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Lars-Peter Clausen (1):
staging: ralink-gdma: Remove incorrect author information
Wenli Looi (1):
staging: rtl8723bs: Fix uninitialized variables
drivers/staging/ralink-gdma/ralink-gdma.c | 2 --
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
next reply other threads:[~2021-06-12 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 15:54 Greg KH [this message]
2021-06-12 19:37 ` [GIT PULL] Staging driver fixes for 5.13-rc6 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=YMTYtya0Sn/JVtz2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.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 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.