linux-kernel - Re: HTC Dream aka. t-mobile g1 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Jun 2009 13:38:52 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	David Miller <davem@...emloft.net>
Cc:	swetland@...gle.com, pavel@....cz, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, san@...roid.com,
	rlove@...gle.com
Subject: Re: HTC Dream aka. t-mobile g1 support

On Thu, Jun 11, 2009 at 05:00:30AM -0700, David Miller wrote:
> From: Russell King - ARM Linux <linux@....linux.org.uk>
> Date: Thu, 11 Jun 2009 12:49:12 +0100
> 
> > I can not keep up with the number of patches that need to be
> > reviewed and ultimately merged.  I know this, and I freely admit it,
> > and I have done so on many occasions.
> 
> Then split up the responsibilities to other people instead of being
> the choke point.  Controlling everything isn't so important.

Don't you think that I've been trying to get other people to be more
involved?

- I've been pushing people to send patches to the relevent mailing
  list(s) and maintainer(s) for years.

- I've been pushing people to send their ARM patches to the ARM
  mailing list rather than directly into the patch system for review
  (it even has a comment telling people this) so that others can get
  involved in reviewing them, and sharing that work load.

Do you think either have been anywhere near successful?

For the most part, the answer is no.  People concentrate on their own
areas, and won't look at someone with a new class of platforms (eg,
the STMP or W90x900 stuff).

I'd absolutely love it if the review load could be shared, but for the
most part it just doesn't happen.  Everyone's far too busy with their
own stuff to help out (and that's a reason that they'll give if tackled
head on about it.)

As I've already said, akpm tried to setup a mutual review between
several ARM folk, but as far as I'm aware, it has so far been 
unsuccessful (exactly why I don't know.)

So to somehow level an accusation at me that I'm tightly controlling this
stuff is way off the mark.  I've been trying to get greater participation
but it's just not happening.

> Or, alternatively, experiment with tools that could potentially make
> you more efficient (patchwork has worked wonders for me).

If patchwork can replace what my patch system does for me (which is
basically to help ensure that patches don't get lost which need
applying - that's different from logging every single patch) then
I'll gladly look at it.  It will mean that some of the sanity checks
on the patch content, which happen automatically with the patch system,
will need to be done manually.

If patchwork just gathers up every patch which has ever been seen on
a mailing list, then stuff will get lost at a higher rate than today
and it will have a negative impact.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/