From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for v3.2-rc2
Date: Wed, 23 Nov 2011 21:15:40 +0000 [thread overview]
Message-ID: <201111232115.41035.arnd@arndb.de> (raw)
In-Reply-To: <20111119194408.GD31337@atomide.com>
On Saturday 19 November 2011, Tony Lindgren wrote:
> Please pull omap fixes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap fixes
>
> Most of this pull request are fixes needed by Tomi for the
> display driver clocking.
>
Hi Tony,
Sorry for the delay on my side, I've only today looked at this series.
The patches all look ok, as far as I can tell, but please rebase
the series to make it easier to see what is going on:
* At least one of the sub-branches is based on a random commit on
Linus' tree. Please always base patches on an -rc for consistency!
* Out of the 20 patches, not one is marked for 'stable' backports.
I really want to make sure this time that all long-standing bugs
get fixed in stable releases, so please go through the list and
add 'Cc: stable at kernel.org' to the ones you want to have backported.
If all patches are actually addressing regressions, just tell me
in the introductory mail next time.
* Since a lot of patches address the dss, it would be nice to have
a separate pull request for those. It's not really important, but
I feel that it's easier to review stuff that is less mixed and
splitting them out should be easy if you rebase the series anyway.
Thanks for your patience,
Arnd
next prev parent reply other threads:[~2011-11-23 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 19:44 [GIT PULL] omap fixes for v3.2-rc2 Tony Lindgren
2011-11-23 21:15 ` Arnd Bergmann [this message]
2011-11-23 22:03 ` Tony Lindgren
2011-11-23 22:22 ` Arnd Bergmann
2011-11-23 23:11 ` Tony Lindgren
2011-11-24 0:42 ` 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=201111232115.41035.arnd@arndb.de \
--to=arnd@arndb.de \
--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).