From: Andrew Lunn <andrew@lunn.ch>
To: Greg KH <greg@kroah.com>
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, 5 Sep 2018 16:51:10 +0200 [thread overview]
Message-ID: <20180905145110.GC28719@lunn.ch> (raw)
In-Reply-To: <20180905142046.GA8396@kroah.com>
> Look at what moved out this, and the past, kernel releases for examples
> (I can't remember the names at the moment, sorry). Another driver just
> got moved last week into the networking tree, so that's another success
> story.
I tend to look at all new network drivers, and i was involved in that
one.
In general, there is no interaction between people working on network
drivers in staging and netdev. So i have no idea what network drivers
are currently in staging. There are no requests to review them to help
get them up to mainline quality. Generally, the first time netdev
hears of them is when somebody submits a patch moving the driver. And
often that patch is created with git format-patch -M, so all we see
are renames, not the actual code. That makes it impossible to actual
review the patch.
So i think it would be useful to add some hints to the documentation
about how to get out of staging. When to get the target subsystem
involved, how to ask for reviews, how to submit it to the target
subsystem, etc.
Andrew
next prev parent reply other threads:[~2018-09-05 15:35 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 [this message]
2018-09-05 14:59 ` Joe Perches
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=20180905145110.GC28719@lunn.ch \
--to=andrew@lunn.ch \
--cc=dan.carpenter@oracle.com \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.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