From: "Sell, Timothy C" <Timothy.Sell@unisys.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Jes Sorensen <Jes.Sorensen@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: "mingo@kernel.org" <mingo@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"timur@freescale.com" <timur@freescale.com>,
"galak@kernel.crashing.org" <galak@kernel.crashing.org>,
"Kershner, David A" <David.Kershner@unisys.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"Arfvidson, Erik" <Erik.Arfvidson@unisys.com>,
"hofrat@osadl.org" <hofrat@osadl.org>,
"dzickus@redhat.com" <dzickus@redhat.com>,
"Curtin, Alexander Paul" <Alexander.Curtin@unisys.com>,
"janani.rvchndrn@gmail.com" <janani.rvchndrn@gmail.com>,
"sudipm.mukherjee@gmail.com" <sudipm.mukherjee@gmail.com>,
"prarit@redhat.com" <prarit@redhat.com>,
"Binder, David Anthony" <David.Binder@unisys.com>,
"nhorman@redhat.com" <nhorman@redhat.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
*S-Par-Maintainer <SParMaintainer@unisys.com>
Subject: RE: new driver for drivers/virt/?
Date: Thu, 19 May 2016 06:22:05 +0000 [thread overview]
Message-ID: <ec2c8f6eacdb45eea4f8787bebc187fc@US-EXCH13-2.na.uis.unisys.com> (raw)
In-Reply-To: <20160518222442.GA15516@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Wednesday, May 18, 2016 6:25 PM
> 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/?
>
> 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 :(
Sorry; I didn't intend to belittle your opinions. Since we want to
push code to drivers/virt/, I figured it would be prudent to get
permission from those folks reported by:
./scripts/get_maintainer.pl -f drivers/virt/
first. That was the intent of my original email, and why I chose
the distribution list I did.
I've never done this before, so I spend quite a lot of time groping
around blindly... ;-(
Tim Sell
>
> > 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:
>
> <snip>
>
> 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
next prev parent reply other threads:[~2016-05-19 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 20:11 Sell, Timothy C
2016-05-18 22:11 ` Thomas Gleixner
2016-05-18 22:24 ` Greg KH
2016-05-19 6:22 ` Sell, Timothy C [this message]
2016-05-18 22:24 ` Sell, Timothy C
2016-05-19 14:44 ` Sell, Timothy C
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=ec2c8f6eacdb45eea4f8787bebc187fc@US-EXCH13-2.na.uis.unisys.com \
--to=timothy.sell@unisys.com \
--cc=Alexander.Curtin@unisys.com \
--cc=David.Binder@unisys.com \
--cc=David.Kershner@unisys.com \
--cc=Erik.Arfvidson@unisys.com \
--cc=Jes.Sorensen@redhat.com \
--cc=SParMaintainer@unisys.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=dzickus@redhat.com \
--cc=galak@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=hofrat@osadl.org \
--cc=hpa@zytor.com \
--cc=janani.rvchndrn@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=nhorman@redhat.com \
--cc=prarit@redhat.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=tglx@linutronix.de \
--cc=timur@freescale.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®