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, devel@linuxdriverproject.org
Subject: [GIT PULL] Staging driver fixes for 4.18-rc7
Date: Thu, 26 Jul 2018 16:19:21 +0200 [thread overview]
Message-ID: <20180726141921.GA14060@kroah.com> (raw)
The following changes since commit 9d3cce1e8b8561fed5f383d22a4d6949db4eadbe:
Linux 4.18-rc5 (2018-07-15 12:49:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-4.18-rc7
for you to fetch changes up to b96fba8d5855c3617adbfb43ca4723a808cac954:
staging: speakup: fix wraparound in uaccess length check (2018-07-16 10:04:11 +0200)
----------------------------------------------------------------
staging driver fixes for 4.18-rc7
Here are 3 small staging driver fixes for 4.18-rc7. One is a revert of
an earlier patch that turned out to be incorrect, one is a fix for the
speakup drivers, and the last a fix for the ks7010 driver to resolve a
regression.
All of these have been in linux-next for a while with no reported
issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Hans de Goede (1):
Revert "staging:r8188eu: Use lib80211 to support TKIP"
Samuel Thibault (1):
staging: speakup: fix wraparound in uaccess length check
Sergio Paracuellos (1):
staging: ks7010: call 'hostif_mib_set_request_int' instead of 'hostif_mib_set_request_bool'
drivers/staging/ks7010/ks_hostif.c | 12 +-
drivers/staging/rtl8188eu/Kconfig | 1 -
drivers/staging/rtl8188eu/core/rtw_recv.c | 161 ++++++++++++++++++--------
drivers/staging/rtl8188eu/core/rtw_security.c | 92 +++++++--------
drivers/staging/speakup/speakup_soft.c | 6 +-
5 files changed, 171 insertions(+), 101 deletions(-)
reply other threads:[~2018-07-26 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180726141921.GA14060@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