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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070405180334.GW24297@atomide.com>
Date:	Thu, 5 Apr 2007 14:03:36 -0400
From:	Tony Lindgren <tony@...mide.com>
To:	Roland Dreier <rdreier@...co.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/90] Post 2.6.21 OMAP update

* Roland Dreier <rdreier@...co.com> [070405 12:32]:
>  > > It would be enormously helpful if instead we got say 15 small patch sets
>  > > which are independant so that a query or NAK means 14 sets get applied
>  > > this time around not zero.
>  > 
>  > I was thinking about merging the patches together more, but the end result
>  > would not be very readable, and we would lose the original author info.
>  > 
>  > Also trying to do this 15 small patches at time would make it hard
>  > to have it all integrated within the two week merge window.
> 
> I think you misunderstood the suggestion.  The idea is that you leave
> the patches basically as-is (modulo any small tweaks required by
> reordering), but rather than one 90-patch series, you divide the
> patches up into independent subsets.  Maybe something like
> 
>  - basic OMAP fixes for bugs in core support
>  - Palm platform stuff
>  - ...other platform stuff
>  - new features
> 
> etc.  then it's easier for people to review the stuff they're
> interested in, and it's easier for at least some of the subsets to get
> applied (which reduces your backlog).

Hmm, yeah I'll see if I could group them a bit. The problem there
is that the patch series contains multiple rounds of "add and fix"
cycles. Pretty much all the non-dependant fixes have already been
applied, BTW.

Tony
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ