public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: devel@linuxdriverproject.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] IIO fixes / Staging driver for 5.4-rc7
Date: Tue, 12 Nov 2019 07:56:29 +0100	[thread overview]
Message-ID: <20191112065629.GA1242198@kroah.com> (raw)
In-Reply-To: <20191112063440.GA15951@infradead.org>

On Mon, Nov 11, 2019 at 10:34:40PM -0800, Christoph Hellwig wrote:
> On Sun, Nov 10, 2019 at 04:43:03PM +0100, Greg KH wrote:
> > The staging driver addition is the vboxsf filesystem, which is the
> > VirtualBox guest shared folder code.  Hans has been trying to get
> > filesystem reviewers to review the code for many months now, and
> > Christoph finally said to just merge it in staging now as it is
> > stand-alone and the filesystem people can review it easier over time
> > that way.
> 
> No, this is absolutely contrary to what I said.  I told Hans to just
> send it to Linus because it is ready and not staging fodder a atll.

Hah, ok, I got that totally wrong.  I'll send a patch moving it to the
"real" part of the kernel now.

thanks,

greg k-h

  reply	other threads:[~2019-11-12  6:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 15:43 [GIT PULL] IIO fixes / Staging driver for 5.4-rc7 Greg KH
2019-11-10 21:35 ` pr-tracker-bot
2019-11-12  6:34 ` Christoph Hellwig
2019-11-12  6:56   ` Greg KH [this message]
2019-11-12 22:54     ` [PATCH] vboxsf: move out of staging to fs/ Greg Kroah-Hartman
2019-11-12 22:54       ` Greg Kroah-Hartman
2019-11-12 23:12       ` Linus Torvalds
2019-11-12 23:12         ` Linus Torvalds
2019-11-13  5:33         ` Greg Kroah-Hartman
2019-11-13  5:33           ` Greg Kroah-Hartman
2019-11-13  8:03         ` Hans de Goede
2019-11-13  8:03           ` Hans de Goede

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=20191112065629.GA1242198@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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