Message-ID: <1512751979.1845.21.camel@perches.com>
Subject: Re: [PATCH v2] drivers: visorbus: move driver out of staging
From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>,
        David Kershner <david.kershner@unisys.com>
Cc: jes.sorensen@gmail.com, linux-kernel@vger.kernel.org,
        driverdev-devel@linuxdriverproject.org, sparmaintainer@unisys.com,
        erik.arfvidson@gmail.com, wadgaonkarsam@gmail.com
Date: Fri, 08 Dec 2017 08:52:59 -0800
In-Reply-To: <20171208153913.GA31823@kroah.com>
References: <1512666667-14981-1-git-send-email-david.kershner@unisys.com>
         <20171208153913.GA31823@kroah.com>
Content-Type: text/plain; charset="ISO-8859-1"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 607
Lines: 13

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?