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.8-rc3
Date: Sat, 27 Jun 2020 13:40:37 +0200 [thread overview]
Message-ID: <20200627114037.GA1637063@kroah.com> (raw)
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-5.8-rc3
for you to fetch changes up to b65a2d8c8614386f7e8d38ea150749f8a862f431:
Staging: rtl8723bs: prevent buffer overflow in update_sta_support_rate() (2020-06-16 21:25:38 +0200)
----------------------------------------------------------------
Staging driver fixes for 5.8-rc3
Here are a small number of tiny staging driver fixes for 5.8-rc3.
Not much here, but there were some reported problems to be fixed:
- 3 wfx driver fixes
- rtl8723bs driver fix
All of these have been in linux-next with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Dan Carpenter (1):
Staging: rtl8723bs: prevent buffer overflow in update_sta_support_rate()
Jérôme Pouiller (3):
staging: wfx: fix AC priority
staging: wfx: drop useless loop
staging: wfx: fix coherency of hif_scan() prototype
drivers/staging/rtl8723bs/core/rtw_wlan_util.c | 4 +++-
drivers/staging/wfx/hif_tx.c | 6 ++++--
drivers/staging/wfx/hif_tx.h | 2 +-
drivers/staging/wfx/queue.c | 21 +++++++++------------
drivers/staging/wfx/scan.c | 6 +++---
5 files changed, 20 insertions(+), 19 deletions(-)
next reply other threads:[~2020-06-27 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 11:40 Greg KH [this message]
2020-06-27 20:25 ` [GIT PULL] Staging driver fixes for 5.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=20200627114037.GA1637063@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