public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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-rc5
Date: Wed, 11 Jul 2018 12:57:02 +0200	[thread overview]
Message-ID: <20180711105702.GA18092@kroah.com> (raw)

The following changes since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:

  Linux 4.18-rc3 (2018-07-01 16:04:53 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.18-rc5

for you to fetch changes up to d59d2f9995d28974877750f429e821324bd603c7:

  staging: r8822be: Fix RTL8822be can't find any wireless AP (2018-07-06 17:44:35 +0200)

----------------------------------------------------------------
Staging fixes for 4.18-rc5

Here are two tiny staging driver fixes for reported issues for 4.18-rc5.

One fixes the r8822be driver to properly work on lots of new laptops,
the other is for the rtl8723bs driver to fix an underflow error.

Both have been in linux-next for a while with no reported issues.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Murray McAllister (1):
      staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data().

Ping-Ke Shih (1):
      staging: r8822be: Fix RTL8822be can't find any wireless AP

 drivers/staging/rtl8723bs/core/rtw_ap.c | 2 +-
 drivers/staging/rtlwifi/rtl8822be/hw.c  | 2 +-
 drivers/staging/rtlwifi/wifi.h          | 1 +
 3 files changed, 3 insertions(+), 2 deletions(-)

                 reply	other threads:[~2018-07-11 10:57 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=20180711105702.GA18092@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