From: David Kershner <david.kershner@unisys.com>
To: <david.kershner@unisys.com>, <gregkh@linuxfoundation.org>,
<jes.sorensen@gmail.com>, <linux-kernel@vger.kernel.org>,
<driverdev-devel@linuxdriverproject.org>,
<sparmaintainer@unisys.com>, <erik.arfvidson@gmail.com>,
<wadgaonkarsam@gmail.com>
Subject: [PATCH 0/2] drivers: Move visorbus from staging to drivers/visorbus
Date: Fri, 17 Nov 2017 12:27:37 -0500 [thread overview]
Message-ID: <1510939659-15039-1-git-send-email-david.kershner@unisys.com> (raw)
This patch series fixes an issue that was reported by Dan Carpenter, moves
the necessary include files to include/linux/visorbus and then moves the
visorbus driver from drivers/staging/unisys to drivers/visorbus.
Greg, thanks for the review of visorbus and for the assistance to get the
driver to this state.
David Kershner (1):
drivers: visorbus: move driver out of staging
Tim Sell (1):
staging: unisys: visorbus: address theoretical int overflows
MAINTAINERS | 2 ++
drivers/Kconfig | 2 ++
drivers/Makefile | 1 +
drivers/staging/unisys/Kconfig | 1 -
drivers/staging/unisys/Makefile | 1 -
drivers/staging/unisys/include/iochannel.h | 3 +--
drivers/staging/unisys/visorhba/visorhba_main.c | 2 +-
drivers/staging/unisys/visorinput/visorinput.c | 2 +-
drivers/staging/unisys/visornic/visornic_main.c | 2 +-
drivers/{staging/unisys => }/visorbus/Kconfig | 4 +++-
drivers/{staging/unisys => }/visorbus/Makefile | 2 --
drivers/{staging/unisys => }/visorbus/controlvmchannel.h | 3 +--
drivers/{staging/unisys => }/visorbus/vbuschannel.h | 2 +-
drivers/{staging/unisys => }/visorbus/visorbus_main.c | 2 +-
drivers/{staging/unisys => }/visorbus/visorbus_private.h | 2 +-
drivers/{staging/unisys => }/visorbus/visorchannel.c | 2 +-
drivers/{staging/unisys => }/visorbus/visorchipset.c | 9 +++++----
.../staging/unisys/include => include/linux/visorbus}/visorbus.h | 0
.../unisys/include => include/linux/visorbus}/visorchannel.h | 0
19 files changed, 22 insertions(+), 20 deletions(-)
rename drivers/{staging/unisys => }/visorbus/Kconfig (90%)
rename drivers/{staging/unisys => }/visorbus/Makefile (81%)
rename drivers/{staging/unisys => }/visorbus/controlvmchannel.h (99%)
rename drivers/{staging/unisys => }/visorbus/vbuschannel.h (98%)
rename drivers/{staging/unisys => }/visorbus/visorbus_main.c (99%)
rename drivers/{staging/unisys => }/visorbus/visorbus_private.h (98%)
rename drivers/{staging/unisys => }/visorbus/visorchannel.c (99%)
rename drivers/{staging/unisys => }/visorbus/visorchipset.c (99%)
rename {drivers/staging/unisys/include => include/linux/visorbus}/visorbus.h (100%)
rename {drivers/staging/unisys/include => include/linux/visorbus}/visorchannel.h (100%)
--
1.9.1
next reply other threads:[~2017-11-17 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 17:27 David Kershner [this message]
2017-11-17 17:27 ` [PATCH 1/2] staging: unisys: visorbus: address theoretical int overflows David Kershner
2017-11-28 14:11 ` Dan Carpenter
2017-11-17 17:27 ` [PATCH 2/2] drivers: visorbus: move driver out of staging David Kershner
2017-11-17 19:17 ` Christoph Hellwig
2017-11-17 21:11 ` Kershner, David A
2017-11-18 10:26 ` Greg KH
2017-11-18 14:30 ` Kershner, David A
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=1510939659-15039-1-git-send-email-david.kershner@unisys.com \
--to=david.kershner@unisys.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=erik.arfvidson@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jes.sorensen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparmaintainer@unisys.com \
--cc=wadgaonkarsam@gmail.com \
/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®