From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] preparation patches for Cortex-M3
Date: Sat, 9 Mar 2013 21:31:59 +0100 [thread overview]
Message-ID: <20130309203159.GM15375@pengutronix.de> (raw)
In-Reply-To: <20130308233733.GD4977@n2100.arm.linux.org.uk>
Hello Russell,
On Fri, Mar 08, 2013 at 11:37:34PM +0000, Russell King - ARM Linux wrote:
> On Thu, Mar 07, 2013 at 04:11:38PM +0100, Uwe Kleine-K?nig wrote:
> > Hello Russell,
> >
> > the following changes since commit 949db153b6466c6f7cad5a427ecea94985927311:
> >
> > Linux 3.8-rc5 (2013-01-25 11:57:28 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.pengutronix.de/git/ukl/linux.git for-next
> >
> > for you to fetch changes up to 6ebd4d038dbb626a43d87db3007e71f92f49d7b3:
> >
> > ARM: stub out read_cpuid and read_cpuid_ext for CPU_CP15=n (2013-01-31 21:44:48 +0100)
> >
> > These are in next since next-20130213 without any problem reports.
> >
> > I currently base my Cortex-M3 stuff on top of these. The complete series
> > still has some problems though that I have to debug first. I'd be glad
> > if you'd pull at least this series for 3.10.
>
> Okay, and you of course did try doing a test-merge with something like
> v3.9-rc1 before sending this pull request, so you know about these
> conflicts - which I've fixed up like this. Does this look sensible?
I should have mentioned the conflict resolution in next is fine. Your's
is slightly different, but even better.
I documented to point out merge conflicts for future pull requests in my
check list, so I expect to do better next time.
Thanks for pulling and the conflict handling
Uwe
prev parent reply other threads:[~2013-03-09 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 15:11 [GIT PULL] preparation patches for Cortex-M3 Uwe Kleine-König
2013-03-08 23:37 ` Russell King - ARM Linux
2013-03-09 20:31 ` Uwe Kleine-König [this message]
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=20130309203159.GM15375@pengutronix.de \
--to=u.kleine-koenig@pengutronix.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).