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, linux-staging@lists.linux.dev
Subject: [GIT PULL] Staging driver fixes for 5.19-rc3
Date: Fri, 17 Jun 2022 10:15:11 +0200 [thread overview]
Message-ID: <Yqw4DynMEtAcZVim@kroah.com> (raw)
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-5.19-rc3
for you to fetch changes up to cd756dafd86ee3a4969906086f3c2537e0c6d9d0:
staging: Also remove the Unisys visorbus.h (2022-06-10 15:36:49 +0200)
----------------------------------------------------------------
Staging driver fixes for 5.19-rc3
Here are some small staging driver fixes for 5.19-rc3 that resolve
reported issues:
- remove visorbus.h which was forgotten in the -rc1 merge where
the code that used it was removed
- olpc_dcon: mark as broken to allow the DRM developers to
evolve the fbdev api properly without having to deal with this
obsolete driver. It will be removed soon if no one steps up
to adopt it and fix the issues with it.
- rtl8723bs driver fix
- r8188eu driver fix to resolve many reports of the driver being
broken with -rc1.
All of these have been in linux-next for a while with no reported
issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Javier Martinez Canillas (1):
staging: olpc_dcon: mark driver as broken
Kees Cook (1):
staging: rtl8723bs: Allocate full pwep structure
Larry Finger (1):
staging: r8188eu: Fix warning of array overflow in ioctl_linux.c
Peter Robinson (1):
staging: Also remove the Unisys visorbus.h
Phillip Potter (1):
staging: r8188eu: fix rtw_alloc_hwxmits error detection for now
drivers/staging/olpc_dcon/Kconfig | 2 +-
drivers/staging/r8188eu/core/rtw_xmit.c | 20 +-
drivers/staging/r8188eu/os_dep/ioctl_linux.c | 2 +-
drivers/staging/rtl8723bs/os_dep/ioctl_linux.c | 6 +-
include/linux/visorbus.h | 344 -------------------------
5 files changed, 11 insertions(+), 363 deletions(-)
delete mode 100644 include/linux/visorbus.h
next reply other threads:[~2022-06-17 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:15 Greg KH [this message]
2022-06-17 15:00 ` 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=Yqw4DynMEtAcZVim@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®