From: "Kershner, David A" <David.Kershner@unisys.com>
To: Joe Perches <joe@perches.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: "jes.sorensen@gmail.com" <jes.sorensen@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
*S-Par-Maintainer <SParMaintainer@unisys.com>,
"erik.arfvidson@gmail.com" <erik.arfvidson@gmail.com>,
"wadgaonkarsam@gmail.com" <wadgaonkarsam@gmail.com>
Subject: RE: [PATCH v2] drivers: visorbus: move driver out of staging
Date: Fri, 8 Dec 2017 21:55:22 +0000 [thread overview]
Message-ID: <CY4PR07MB3176D381BAAE33037A01E75DF0300@CY4PR07MB3176.namprd07.prod.outlook.com> (raw)
In-Reply-To: <1512751979.1845.21.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]
> -----Original Message-----
> From: Joe Perches [mailto:joe@perches.com]
> Sent: Friday, December 8, 2017 11:53 AM
> To: Greg KH <gregkh@linuxfoundation.org>; Kershner, David A
> <David.Kershner@unisys.com>
> Cc: jes.sorensen@gmail.com; linux-kernel@vger.kernel.org; driverdev-
> devel@linuxdriverproject.org; *S-Par-Maintainer
> <SParMaintainer@unisys.com>; erik.arfvidson@gmail.com;
> wadgaonkarsam@gmail.com
> Subject: Re: [PATCH v2] drivers: visorbus: move driver out of staging
>
> On Fri, 2017-12-08 at 16:39 +0100, Greg KH wrote:
> > On Thu, Dec 07, 2017 at 12:11:07PM -0500, David Kershner wrote:
> > > Move the visorbus driver out of staging
(drivers/staging/unisys/visorbus)
> > > and to drivers/visorbus. Modify the configuration and makefiles so
they
> > > now reference the new location. The s-Par header file visorbus.h that
is
> > > referenced by all s-Par drivers, is being moved into include/linux.
>
> Perhaps moving visorbus.h and visorbus_private.h to
> drivers/visorbus would be better than adding more
> relatively localized #include files to include/linux/
>
> what about controlvmchannel?
>
The file visorbus.h is currently included by 4 drivers: visorbus and 3
other drivers that are staying in staging for now, but we plan to move out
soon.
The files visorbus_private.h and controlvmchannel.h are only used by the
visorbus driver and belong solely in the visorbus directory, no one should
be including them besides the visorbus driver.
David Kershner
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7862 bytes --]
next prev parent reply other threads:[~2017-12-08 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 17:11 [PATCH v2] drivers: visorbus: move driver out of staging David Kershner
2017-12-08 15:39 ` Greg KH
2017-12-08 16:52 ` Joe Perches
2017-12-08 21:55 ` Kershner, David A [this message]
2017-12-08 22:13 ` Joe Perches
2017-12-09 17:40 ` Greg KH
2017-12-08 18:32 ` Dan Carpenter
2017-12-08 21:57 ` Kershner, David A
2017-12-12 9:13 ` Christoph Hellwig
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=CY4PR07MB3176D381BAAE33037A01E75DF0300@CY4PR07MB3176.namprd07.prod.outlook.com \
--to=david.kershner@unisys.com \
--cc=SParMaintainer@unisys.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=erik.arfvidson@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jes.sorensen@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).