From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add files under drivers/virt/* to CHAR and MISC DRIVERS section
Date: Mon, 28 Aug 2017 16:26:13 +0200 [thread overview]
Message-ID: <20170828142613.GA21720@kroah.com> (raw)
In-Reply-To: <43c3b97f-20c0-9232-432e-96af6bf369f6@redhat.com>
On Mon, Aug 28, 2017 at 04:13:38PM +0200, Hans de Goede wrote:
> Hi,
>
> On 28-08-17 16:08, Greg Kroah-Hartman wrote:
> > On Fri, Aug 25, 2017 at 03:11:25PM +0200, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 25-08-17 15:10, Greg Kroah-Hartman wrote:
> > > > On Fri, Aug 25, 2017 at 01:56:23PM +0200, Hans de Goede wrote:
> > > > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > Cc: Arnd Bergmann <arnd@arndb.de>
> > > > > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > > > > ---
> > > > > MAINTAINERS | 1 +
> > > > > 1 file changed, 1 insertion(+)
> > > > >
> > > > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > > > index 6a349b5c0c2a..db633caa5a1d 100644
> > > > > --- a/MAINTAINERS
> > > > > +++ b/MAINTAINERS
> > > > > @@ -3284,6 +3284,7 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> > > > > S: Supported
> > > > > F: drivers/char/*
> > > > > F: drivers/misc/*
> > > > > +F: drivers/virt/*
> > > >
> > > > Really? I'm now in charge of this directory too? That's news to me...
> > >
> > > This was suggested by Arnd, as he preferred putting the vboxguest driver
> > > under drivers/virt rather then drivers/misc. Note that currently there is
> > > only one .c file under drivers/virt: fsl_hypervisor.c
> >
> > Ok, but how about we wait until there is more than one file in here?
>
> That is fine by me.
>
> > And what happened to all of the other "virt" drivers, why are they not here?
>
> Some vmware drivers are currently under drivers/misc, Arnd's proposal was
> to move those to drivers/virt. virtio and hyperv have their own subsys
> dirs.
>
> > Perhaps using this directory isn't really a good idea?
>
> I started out with the same idea which is why v1 of my RFC posting of the
> vboxguest driver used drivers/misc, alternatively we could move the single
> driver currently under drivers/virt to drivers/misc and stop using
> drivers/virt.
>
> > I don't know...
>
> Arnd indicated he has a preference for using drivers/virt for vboxguest +
> the vmware drivers, I'm fine either way. This really is a bit of a bikeshed-
> ish discussion IMHO. So if you and/or Arnd pick one I will happily follow
> whatever you choose.
Ah, if we move the vmware ones there, I have no problem with it, I
missed that part of the discussion.
thanks,
greg k-h
prev parent reply other threads:[~2017-08-28 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 11:56 [PATCH] MAINTAINERS: Add files under drivers/virt/* to CHAR and MISC DRIVERS section Hans de Goede
2017-08-25 13:10 ` Greg Kroah-Hartman
2017-08-25 13:11 ` Hans de Goede
2017-08-28 14:08 ` Greg Kroah-Hartman
2017-08-28 14:13 ` Hans de Goede
2017-08-28 14:26 ` Greg Kroah-Hartman [this message]
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=20170828142613.GA21720@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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