From: Roland Dreier <rdreier@cisco.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/90] Post 2.6.21 OMAP update
Date: Thu, 05 Apr 2007 09:31:57 -0700 [thread overview]
Message-ID: <adar6qybx4y.fsf@cisco.com> (raw)
In-Reply-To: <20070405132144.GC24297@atomide.com> (Tony Lindgren's message of "Thu, 5 Apr 2007 09:21:48 -0400")
> > 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).
- R.
next prev parent reply other threads:[~2007-04-05 16:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 17:46 [PATCH 0/90] Post 2.6.21 OMAP update Tony Lindgren
2007-04-04 17:46 ` [PATCH 1/90] ARM: OMAP: Place SMS and SDRC into smart idle mode Tony Lindgren
2007-04-04 17:46 ` [PATCH 2/90] ARM: OMAP: Force APLLs always active Tony Lindgren
2007-04-04 17:46 ` [PATCH 3/90] ARM: OMAP: Add DMA IRQ sanity checks Tony Lindgren
2007-04-04 17:46 ` [PATCH 4/90] ARM: OMAP: Enable 24xx GPIO autoidling Tony Lindgren
2007-04-04 17:46 ` [PATCH 5/90] ARM: OMAP: Add function to print clock usecounts Tony Lindgren
2007-04-04 17:46 ` [PATCH 6/90] ARM: OMAP: Enable serial idling and wakeup features Tony Lindgren
2007-04-04 17:46 ` [PATCH 7/90] ARM: OMAP: Optimize INTC register accesses and enable autoidling Tony Lindgren
2007-04-04 17:46 ` [PATCH 8/90] ARM: OMAP: FB: add controller platform data Tony Lindgren
2007-04-04 18:27 ` [PATCH 0/90] Post 2.6.21 OMAP update Tony Lindgren
2007-04-04 18:39 ` Randy Dunlap
2007-04-04 18:44 ` Tony Lindgren
2007-04-04 21:44 ` Alan Cox
2007-04-05 13:21 ` Tony Lindgren
2007-04-05 16:31 ` Roland Dreier [this message]
2007-04-05 18:03 ` Tony Lindgren
2007-04-05 18:29 ` Roland Dreier
2007-04-09 21:45 ` Tony Lindgren
2007-04-05 20:27 ` Alan Cox
2007-04-06 7:18 ` Russell King
2007-04-09 21:49 ` Tony Lindgren
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=adar6qybx4y.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox