ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg KH <greg@kroah.com>, Takashi Iwai <tiwai@suse.de>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] How can we treat staging drivers better?
Date: Wed, 05 Sep 2018 07:59:30 -0700	[thread overview]
Message-ID: <11c23ee895802b2f9e82bd90e23d6a30fe1f060c.camel@perches.com> (raw)
In-Reply-To: <20180905142046.GA8396@kroah.com>

On Wed, 2018-09-05 at 16:20 +0200, Greg KH wrote:
> I always push code to the
> subsystem-specific maintainers when they are to "graduate", I never
> merge things behind maintainers backs.

Recently, there was an attempt to move code from 'staging'
to a more mainline tree that needed to be reviewed by the
nominal subsystem maintainer.

https://www.spinics.net/lists/netdev/msg520443.html

I believe the nominal maintainer(s) should be involved
somewhat earlier than that.

  parent reply	other threads:[~2018-09-06  0:27 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 [this message]
2018-09-05 14:08   ` Sean Paul
2018-09-05 14:22     ` Greg KH
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=11c23ee895802b2f9e82bd90e23d6a30fe1f060c.camel@perches.com \
    --to=joe@perches.com \
    --cc=dan.carpenter@oracle.com \
    --cc=greg@kroah.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tiwai@suse.de \
    /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