ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sean Paul <seanpaul@chromium.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] How can we treat staging drivers better?
Date: Wed, 5 Sep 2018 16:22:25 +0200	[thread overview]
Message-ID: <20180905142225.GA8757@kroah.com> (raw)
In-Reply-To: <CAOw6vbKa+85J0gDbh0Fj3GYQFcDma_qPPYjSUKxYvjmHvO3a5A@mail.gmail.com>

On Wed, Sep 05, 2018 at 10:08:00AM -0400, Sean Paul wrote:
> > Which ones are you interested in?  I'd always prefer to hand off staging
> > drivers to an existing subsystem but it's not always clear who that
> > should be.
> 
> In the case of vboxvideo, we won't accept it in drm since it's not an
> atomic driver. staging's bar for entry was lower, so the driver was
> stuck in there. Perhaps we would have been better to take it in drm
> behind a config, but that's not ideal either.

for vboxvideo, I am pretty sure I got an "it's ok to put it there" from
the DRM maintainers before I accepted it.  So they know it is there :)

If it's not ever going to be merged, maybe we should just drop it?

thanks,

greg k-h

  reply	other threads:[~2018-09-05 14:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 13:35 Takashi Iwai
2018-09-05 13:55 ` Dan Carpenter
2018-09-05 14:03   ` Takashi Iwai
2018-09-05 14:20     ` Greg KH
2018-09-05 14:41       ` Takashi Iwai
2018-09-05 14:59         ` Shuah Khan
2018-09-05 14:51       ` Andrew Lunn
2018-09-05 14:59       ` Joe Perches
2018-09-05 14:08   ` Sean Paul
2018-09-05 14:22     ` Greg KH [this message]
2018-09-05 14:29       ` Sean Paul
2018-09-05 15:35         ` Daniel Vetter
2018-09-05 16:21 ` James Bottomley
2018-09-05 16:35   ` Daniel Vetter
2018-09-07 19:44 ` Mauro Carvalho Chehab
2018-09-08  8:45   ` Jonathan Cameron
2018-09-10 18:49     ` Takashi Iwai
2018-09-10 18:52   ` Takashi Iwai
2018-09-10 18:58     ` Laurent Pinchart
2018-09-10 19:22       ` Tim.Bird
2018-09-10 20:51         ` Laurent Pinchart
2018-09-11  0:30         ` Mauro Carvalho Chehab
2018-09-11  9:13         ` Greg KH

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=20180905142225.GA8757@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=seanpaul@chromium.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