From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX features for next
Date: Thu, 8 Sep 2011 17:20:18 +0200 [thread overview]
Message-ID: <201109081720.18929.arnd@arndb.de> (raw)
In-Reply-To: <20110906192229.GK28816@pengutronix.de>
On Tuesday 06 September 2011, Uwe Kleine-K?nig wrote:
> if I remember correctly you don't mind non-fast-forward updates?! If I'm
> wrong just tell me.
Right, I can take a limited number of those at least. I want a reasonable
git history, not a stainless one ;-)
> Compared to Sascha's pull request this mail is a reply to, the following
> changed:
>
> - squash a patch by Jason Liu <jason.hui@linaro.org> into
> d27536c6619221528114746317def345467a3e80 fixing a build failure for
> mx25 (1314623624-9999-1-git-send-email-jason.hui at linaro.org)
> - squash a patch by Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
> into 236c4e8be436380b5354fe0d7facf94688e024ec fixing the resource
> size for pata_imx devices (20110827131911.571434313 at rtp-net.org)
> - two new patches:
> "ARM: mx51/efika: Configure esdhc cd/wp on efika mx/sb" and "ARM: mx5: fix clock
> usage for suspend" both by Arnaud Patard.
>
> I choosed to squash the two fixes to ease bisection.
> Though the 2nd patch by Arnaud fixes suspend, I think it's not necessary
> to go in before v3.1.
There were a few other pull requests that I haven't taken yet since
master.kernel.org is down. If the general feeling is that I should take
at least the bug fixes, I can start a branch on the linaro server for that.
Arnd
next prev parent reply other threads:[~2011-09-08 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 11:56 [GIT PULL] i.MX features for next Sascha Hauer
2011-08-26 8:26 ` Sascha Hauer
2011-08-26 15:53 ` Arnd Bergmann
2011-09-06 19:22 ` Uwe Kleine-König
2011-09-08 15:20 ` Arnd Bergmann [this message]
2011-09-08 18:17 ` Nicolas Pitre
2011-09-10 21:13 ` Arnd Bergmann
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=201109081720.18929.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.