From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Pull request mxc
Date: Mon, 26 Jul 2010 10:28:55 +0100 [thread overview]
Message-ID: <20100726092855.GA20737@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100726090014.GQ14113@pengutronix.de>
On Mon, Jul 26, 2010 at 11:00:14AM +0200, Sascha Hauer wrote:
> 160 files changed, 6547 insertions(+), 3276 deletions(-)
I get:
160 files changed, 6530 insertions(+), 3265 deletions
which seems to be down to this difference between your diffstat and mine:
> arch/arm/mach-mx3/mach-mx31lilly.c | 48 +-
arch/arm/mach-mx3/mach-mx31lilly.c | 20 +-
This seems to be down to 4d5d859 (ARM: mx3: mx31lilly: fix build error for
!CONFIG_USB_ULPI).
next prev parent reply other threads:[~2010-07-26 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 9:00 Pull request mxc Sascha Hauer
2010-07-26 9:28 ` Russell King - ARM Linux [this message]
2010-07-26 10:32 ` Russell King - ARM Linux
2010-07-26 12:00 ` Sascha Hauer
2010-07-26 13:46 ` Sascha Hauer
2010-07-28 7:44 ` Sascha Hauer
2010-07-27 5:09 ` Baruch Siach
2010-07-28 7:12 ` Sascha Hauer
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=20100726092855.GA20737@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).