From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751478AbcERWYp (ORCPT ); Wed, 18 May 2016 18:24:45 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:44630 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751081AbcERWYo (ORCPT ); Wed, 18 May 2016 18:24:44 -0400 Date: Wed, 18 May 2016 15:24:42 -0700 From: Greg KH To: Thomas Gleixner Cc: "Sell, Timothy C" , "mingo@kernel.org" , "dave.hansen@linux.intel.com" , "timur@freescale.com" , "galak@kernel.crashing.org" , "Kershner, David A" , "corbet@lwn.net" , "mingo@redhat.com" , "hpa@zytor.com" , "Arfvidson, Erik" , "hofrat@osadl.org" , "dzickus@redhat.com" , "Curtin, Alexander Paul" , "janani.rvchndrn@gmail.com" , "sudipm.mukherjee@gmail.com" , "prarit@redhat.com" , "Binder, David Anthony" , "nhorman@redhat.com" , "dan.j.williams@intel.com" , "linux-kernel@vger.kernel.org" , "linux-doc@vger.kernel.org" , "driverdev-devel@linuxdriverproject.org" , *S-Par-Maintainer , Jes Sorensen Subject: Re: new driver for drivers/virt/? Message-ID: <20160518222442.GA15516@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 19, 2016 at 12:11:46AM +0200, Thomas Gleixner wrote: > On Wed, 18 May 2016, Sell, Timothy C wrote: > > We have a bus driver currently in drivers/staging/unisys/visorbus/ that > > we are trying to get out of staging and into the kernel proper. Since > > "visorbus" is a driver to host a virtual bus presented to a Linux guest > > in a hypervisor environment (refer to > > drivers/staging/unisys/Documentation/overview.txt for more details), > > Greg KH and Jes Sorensen have suggested the possibility that drivers/virt/ > > might be a good place for visorbus. But right now, we see that the only > > driver under drivers/virt/ is the Freescale hypervisor environment, which > > made us wonder whether this was really the correct place. > > > > Would you have any guidance for us? > > Our intent is to push our visorbus out of staging immediately following > > the current merge window. > > What's the problem with Gregs and Jes suggestion? I don't see any. Neither do I, odd that they wanted a third opinion :( > There is bigger fish to fry than the final place of this driver. I had just a > peek at the staging code and there is enough stuff which wants to be cleaned > up before moving anywhere. I don't have time to do a proper review now, but > here are a few hints upfront: I don't think anyone has given a good review of the code yet, I know it's been a long time for me. It's on my todo list, but that's not going to happen until way after 4.7-rc1 is out. Thanks for this initial list. greg k-h