From: mzoran@crowfest.net (Michael Zoran)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: extend Raspberry Pi entry
Date: Sun, 29 Jan 2017 13:41:49 -0800 [thread overview]
Message-ID: <1485726109.30797.5.camel@crowfest.net> (raw)
In-Reply-To: <20170129210611.k46ey35py3ht3fe7@tarshish>
On Sun, 2017-01-29 at 23:06 +0200, Baruch Siach wrote:
> Hi Michael,
>
> On Sun, Jan 29, 2017 at 12:52:30PM -0800, Michael Zoran wrote:
> > On Sun, 2017-01-29 at 22:08 +0200, Baruch Siach wrote:
> > > Add bcm2836 (Raspberry Pi 2) and bcm2837 (Raspberry Pi 3).
> > >
> > > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > > ---
> > > ?MAINTAINERS | 4 ++--
> > > ?1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 26edd832c64e..d69449735876 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -2612,7 +2612,7 @@ N: bcm216*
> > > ?N: kona
> > > ?F: arch/arm/mach-bcm/
> > > ?
> > > -BROADCOM BCM2835 ARM ARCHITECTURE
> > > +BROADCOM BCM2835/BCM2836/BCM2837 ARM ARCHITECTURE
> > > ?M: Stephen Warren <swarren@wwwdotorg.org>
> > > ?M: Lee Jones <lee@kernel.org>
> > > ?M: Eric Anholt <eric@anholt.net>
> > > @@ -2620,7 +2620,7 @@ L: linux-rpi-kernel at lists.infradead.
> > > org
> > > (moderated for non-subscribers)
> > > ?L: linux-arm-kernel at lists.infradead.org (moderated for
> > > non-
> > > subscribers)
> > > ?T: git
> > > git://git.kernel.org/pub/scm/linux/kernel/git/rpi/linux-rpi.git
> > > ?S: Maintained
> > > -N: bcm2835
> > > +N: bcm283[5-7x]
> > > ?F: drivers/staging/vc04_services
> > > ?
> > > ?BROADCOM BCM47XX MIPS ARCHITECTURE
> >
> > This is all cool and whatnot, but being new I'm a bit confused how
> > this
> > works.
> >
> > 1. Is everything still going to be e-mail based, because the e-mail
> > based system could use some improvement.
>
> Kernel development is email based. See "Why kernel development still
> uses?
> email"[1]. What would you like to see improved?
>
>
No offense to any of the maintainers, but the e-mail system is
optimized for a very large number of very, very small changes. It isn't
optimized for large changes. In a way it tends to discourage any kind
of big improvements.
The idea of checking in a very large number of small patches makes
sense for auditing. And yes having both isn't totally possible, so I
don't know really where the line should go between the two. But taking
things to one extreme or the other doesn't make sense either.
next prev parent reply other threads:[~2017-01-29 21:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 20:08 [PATCH] MAINTAINERS: extend Raspberry Pi entry Baruch Siach
2017-01-29 20:52 ` Michael Zoran
2017-01-29 21:06 ` Baruch Siach
2017-01-29 21:41 ` Michael Zoran [this message]
2017-01-29 21:52 ` Baruch Siach
2017-01-29 22:02 ` Michael Zoran
2017-01-29 22:24 ` Michael Zoran
2017-01-30 7:56 ` Uwe Kleine-König
2017-01-30 8:09 ` Michael Zoran
2017-01-30 8:51 ` Uwe Kleine-König
2017-01-30 9:01 ` Michael Zoran
2017-01-29 21:06 ` Stefan Wahren
2017-01-29 21:25 ` Michael Zoran
2017-01-30 17:03 ` Stephen Warren
2017-01-31 19:49 ` Eric Anholt
2017-02-01 5:21 ` Stephen Warren
2017-02-01 19:51 ` Eric Anholt
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=1485726109.30797.5.camel@crowfest.net \
--to=mzoran@crowfest.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).