From: Tony Lindgren <tony@atomide.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/90] Post 2.6.21 OMAP update
Date: Wed, 4 Apr 2007 14:44:57 -0400 [thread overview]
Message-ID: <20070404184455.GL29129@atomide.com> (raw)
In-Reply-To: <20070404113925.da221efc.randy.dunlap@oracle.com>
* Randy Dunlap <randy.dunlap@oracle.com> [070404 14:37]:
> On Wed, 4 Apr 2007 14:27:30 -0400 Tony Lindgren wrote:
>
> > * Tony Lindgren <tony@atomide.com> [070404 14:02]:
> > > Hi all,
> > >
> > > Attached is a rather large OMAP update for post 2.6.21.
> > >
> > > OMAP is a series of ARM processors from Texas Instruments
> > > used in various cell phones and PDAs.
> > >
> > > The patch series is based on code that has been brewing
> > > in the linux-omap tree since last fall.
> > >
> > > We'd like to switch the linux-omap tree to use the mainline
> > > tree for core omap stuff, and this series attemps to do it
> > > for most part.
> > >
> > > As the patch series is big, Andrew Morton asked me to post
> > > it to LKML instead of linux-arm-kernel list for a wider review,
> > > so please comment on the patches if you have a chance!
> > >
> > > The patches touch only omap specific code at:
> > >
> > > arch/arm/Kconfig
> > > arch/arm/plat-omap
> > > arch/arm/mach-omap1
> > > arch/arm/mach-omap2
> > > include/asm-arm/arch-omap
> >
> > Looks like using git-send-email --chain-reply-to with this many
> > messages is not a good idea... The threading gets nested too wide :)
>
> That's only a problem when there are <too many> patches to be
> reviewed. Hence, do more frequent postings of fewer patches per series.
> That will likely also get you more reviewers.
Yeah, I agree.. We've already missed two merge windows because of the
large patch set :( The problem is that patch set just keeps growing.
Things should be to normal small patch sets once this pile is dealt
with.
Regards,
Tony
next prev parent reply other threads:[~2007-04-04 18:45 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 [this message]
2007-04-04 21:44 ` Alan Cox
2007-04-05 13:21 ` Tony Lindgren
2007-04-05 16:31 ` Roland Dreier
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=20070404184455.GL29129@atomide.com \
--to=tony@atomide.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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