From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Rapoport <mike.rapoport@gmail.com>
Cc: Joe Perches <joe@perches.com>, Eric Paris <eparis@redhat.com>,
"Luck, Tony" <tony.luck@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ksummit-2010-discuss@lists.linux-foundation.org"
<ksummit-2010-discuss@lists.linux-foundation.org>,
"mingo@elte.hu" <mingo@elte.hu>
Subject: Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
Date: Wed, 1 Sep 2010 11:15:18 +0100 [thread overview]
Message-ID: <20100901101518.GB17491@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTimuWwneVz=+5uPK=N7gQ2=TCWC2jj7ErNg0CedN@mail.gmail.com>
On Wed, Sep 01, 2010 at 01:03:07PM +0300, Mike Rapoport wrote:
> On Wed, Sep 1, 2010 at 11:54 AM, Mark Brown
> > My experience is that there's an awful lot of people working with
> > whatever kernel has been provided by their vendor rather than getting
> > kernels direct from kernel.org and they tend to only look as far as the
> > tarball (or other package) they got.
> People that are working with vendor provided kernels do not tend to
> contribute upstream. And those who want to contribute will find what
> MAINTAINERS is.
While the majority of people won't contribute upstream some do, or come
looking for support, and MAINTAINERS doesn't seem entirely reliable. I
think some people are expecting it to be for maintainers rather than a
list of them.
next prev parent reply other threads:[~2010-09-01 10:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 15:45 [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list Paul E. McKenney
2010-08-26 15:51 ` Jiri Kosina
2010-08-26 16:03 ` [PATCH] MAINTAINERS: add W: todo lists Joe Perches
2010-08-26 15:51 ` [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list Joe Perches
2010-08-26 16:14 ` Paul E. McKenney
2010-08-26 16:18 ` Joe Perches
2010-08-26 16:25 ` [Ksummit-2010-discuss] " James Bottomley
2010-08-26 16:29 ` Randy Dunlap
2010-08-26 16:34 ` James Bottomley
2010-08-26 16:38 ` Arjan van de Ven
2010-08-26 16:42 ` Jiri Kosina
2010-08-26 17:00 ` Dmitry Torokhov
2010-08-31 17:23 ` Steven Rostedt
2010-08-31 23:02 ` Paul E. McKenney
2010-08-31 23:17 ` Steven Rostedt
2010-08-31 23:19 ` Rafael J. Wysocki
2010-08-31 23:25 ` Luck, Tony
2010-08-31 23:46 ` Joe Perches
2010-09-01 0:23 ` Eric Paris
2010-09-01 0:34 ` Joe Perches
2010-09-01 8:54 ` Mark Brown
2010-09-01 10:03 ` Mike Rapoport
2010-09-01 10:15 ` Mark Brown [this message]
2010-09-01 10:02 ` Alan Cox
2010-08-27 9:19 ` Avi Kivity
2010-08-26 16:30 ` Joe Perches
2010-08-26 16:45 ` Joe Perches
2010-08-26 16:50 ` Paul E. McKenney
2010-08-26 23:00 ` Sarah Sharp
2010-08-26 23:23 ` Paul E. McKenney
2010-08-30 1:40 ` Neil Brown
2010-08-30 15:19 ` Eric Van Hensbergen
2010-08-26 23:30 ` Joe Perches
2010-08-26 20:47 ` [rfc] MAINTAINERS: Remove broken URLs Joe Perches
2010-08-26 20:49 ` Roland Dreier
2010-08-26 22:28 ` Justin P. Mattock
2010-08-26 22:37 ` Joe Perches
2010-08-26 22:45 ` Justin P. Mattock
2010-08-26 22:38 ` rdunlap
2010-08-27 13:46 ` John W. Linville
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=20100901101518.GB17491@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=eparis@redhat.com \
--cc=joe@perches.com \
--cc=ksummit-2010-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.rapoport@gmail.com \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.