linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Michael Thayer <michael.thayer@oracle.com>,
	"Knut St . Osmundsen" <knut.osmundsen@oracle.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC 0/2] Add Virtual Box vboxguest and vboxsf guest drivers to the mainline kernel
Date: Fri, 25 Aug 2017 13:53:12 +0200	[thread overview]
Message-ID: <4e1933d6-e1b9-c94c-df56-696f4ea21bf4@redhat.com> (raw)
In-Reply-To: <CAK8P3a1Y2rQahdQRP9+1Hj2bZ0jj5zVwhnUkyMA4F=8mEVE5gA@mail.gmail.com>

Hi,

On 11-08-17 21:34, Arnd Bergmann wrote:
> On Fri, Aug 11, 2017 at 7:43 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> On 11-08-17 18:32, Arnd Bergmann wrote:
>>> On Fri, Aug 11, 2017 at 6:09 PM, Hans de Goede <hdegoede@redhat.com>
>>> wrote:
>>>> On 11-08-17 18:02, Arnd Bergmann wrote:
>>> How about adding it to drivers/virt/ then?
>>
>>
>> That as actually my first choice, but there is only the 1 driver there
>> now, so I was thinking that we should move that 1 driver out of there
>> and get rid of it actually :)
>>
>> But as said it was my first choice, so maybe it should go there and then
>> over time we can move all the things you've listed there (assuming anyone
>> finds the time to do this).
>>
>> One issues with drivers/virt is no-one is listed for it in MAINTAINERS...
> 
> Maybe we could add it to the "CHAR and MISC DRIVERS" section
> in the absence of any other subsystem for it, if you want a well-defined
> path for where to send patches.

That sounds like a good plan, I will send out a MAINTAINERS patch adding
drivers/misc/* to the files list for the "CHAR and MISC DRIVERS" section.

Regards,

Hans

      reply	other threads:[~2017-08-25 11:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11 13:23 [RFC 0/2] Add Virtual Box vboxguest and vboxsf guest drivers to the mainline kernel Hans de Goede
2017-08-11 13:23 ` [RFC 1/2] misc: Add vboxguest driver for Virtual Box Guest integration Hans de Goede
2017-08-11 21:23   ` Arnd Bergmann
2017-08-12 21:56     ` Hans de Goede
2017-08-12 23:22       ` Greg Kroah-Hartman
2017-08-14  7:38       ` Hans de Goede
2017-08-14  9:30       ` Arnd Bergmann
2017-08-14 12:15         ` Hans de Goede
2017-08-21 11:43           ` Hans de Goede
2017-08-21 12:04             ` Hans de Goede
2017-08-11 13:23 ` [RFC 2/2] fs: Add VirtualBox guest shared folder (vboxsf) support Hans de Goede
2017-08-11 15:44 ` [RFC 0/2] Add Virtual Box vboxguest and vboxsf guest drivers to the mainline kernel Greg Kroah-Hartman
2017-08-11 16:02 ` Arnd Bergmann
2017-08-11 16:09   ` Hans de Goede
2017-08-11 16:32     ` Arnd Bergmann
2017-08-11 17:43       ` Hans de Goede
2017-08-11 19:34         ` Arnd Bergmann
2017-08-25 11:53           ` Hans de Goede [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=4e1933d6-e1b9-c94c-df56-696f4ea21bf4@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=knut.osmundsen@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.thayer@oracle.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).