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 4.17-rc3 - take 2
Date: Fri, 27 Apr 2018 16:40:43 +0200 [thread overview]
Message-ID: <20180427144043.GA9154@kroah.com> (raw)
Now with the correct message:
------------------------------
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.17-rc3
for you to fetch changes up to b00e2fd10429eddf4a181ad30af010e56c2303f9:
staging: wilc1000: fix NULL pointer exception in host_int_parse_assoc_resp_info() (2018-04-23 15:57:38 +0200)
----------------------------------------------------------------
Staging fixes for 4.17-rc3
Here are 2 staging driver fixups for 4.17-rc3.
The first is the remaining stragglers of the irda code removal that you
pointed out during the merge window. The second is a fix for the
wilc1000 driver due to a patch that got merged in 4.17-rc1.
Both of these have been in linux-next for a while with no reported
issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Ajay Singh (1):
staging: wilc1000: fix NULL pointer exception in host_int_parse_assoc_resp_info()
Greg Kroah-Hartman (1):
staging: irda: remove remaining remants of irda code removal
Documentation/ioctl/ioctl-number.txt | 2 --
Documentation/networking/ip-sysctl.txt | 15 ---------------
Documentation/process/magic-number.rst | 3 ---
MAINTAINERS | 10 ----------
drivers/staging/wilc1000/host_interface.c | 2 +-
include/uapi/linux/sysctl.h | 18 ------------------
kernel/sysctl_binary.c | 20 +-------------------
7 files changed, 2 insertions(+), 68 deletions(-)
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
reply other threads:[~2018-04-27 14:40 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=20180427144043.GA9154@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
Powered by JetHome