From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap updates for 2.6.40
Date: Fri, 27 May 2011 14:04:19 +0300 [thread overview]
Message-ID: <20110527110416.GG27962@atomide.com> (raw)
In-Reply-To: <20110527063304.GA27962@atomide.com>
* Tony Lindgren <tony@atomide.com> [110527 09:29]:
> * Koen Kooi <koen@dominion.thruhere.net> [110526 19:02]:
> >
> > Op 26 mei 2011, om 13:39 heeft Tony Lindgren het volgende geschreven:
> >
> > > Hi Linus,
> > >
> > > Please pull omap updates for this merge window from:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-for-linus
> > >
> > > This contains clean-up to shrink down omap specific code a bit. Also included
> > > are some fixes. But basically no new code at this point.
> >
> > What about updates to board files? Like adding support for the xM rev C to board-omap3beagle.c.
>
> Sorry we're doing only code coalescing and fixes for this merge window as
> discussed on LAKML. Otherwise it's hard to see the code coalescing in the
> diffstats, so new code will need to wait a bit.
>
> I'll take a look and see if we can justify some fix like trivial patches
> like the revision detection patches during the -rc cycle.
Koen, the patch above needs to be refreshed to apply to current mainline
kernel. It also seems to contain some whitespace errors.
Care to refresh it and repost?
Thanks,
Tony
next prev parent reply other threads:[~2011-05-27 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 11:39 [GIT PULL] omap updates for 2.6.40 Tony Lindgren
2011-05-26 12:14 ` Igor Grinberg
2011-05-26 12:24 ` Tony Lindgren
2011-05-26 12:52 ` Igor Grinberg
2011-05-26 12:55 ` Tony Lindgren
2011-05-26 16:06 ` Koen Kooi
2011-05-27 6:33 ` Tony Lindgren
2011-05-27 11:04 ` Tony Lindgren [this message]
2011-05-27 12:22 ` Koen Kooi
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=20110527110416.GG27962@atomide.com \
--to=tony@atomide.com \
--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).