From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL 5/8] ARM: tegra: SCU base rework
Date: Thu, 31 Jan 2013 21:46:10 -0700 [thread overview]
Message-ID: <510B4892.3050900@wwwdotorg.org> (raw)
In-Reply-To: <CAOesGMjjgz7Am7-D_fQHqgLX=G+Wc_LKL-GYMHd1-NzVC-DUfA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 01/31/2013 09:35 PM, Olof Johansson wrote:
> On Thu, Jan 31, 2013 at 8:32 PM, Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org> wrote:
>> On Wed, Jan 30, 2013 at 02:42:36PM -0700, Stephen Warren wrote:
>>> Tegra currently relies on the SCU to determine the number of CPU
>>> cores, and also hard-codes the SCU physical address.
>>>
>>> This series adds a /cpus node to the Tegra device tree, and updates
>>> the code to rely solely on that to determine the CPU count. A new
>>> API is introduced to query for the existence of SCU registers, and the
>>> SCU register address. Tegra and OMAP2 are converted to use these new
>>> APIs.
>>>
>>> This pull request is based on a merge of v3.8-rc3, and arm-soc's
>>> depends/rmk-perf branch.
>>
>> This one looks like it should also be based on your cleanup, since it has
>> conflicts with it. Please rebase accordingly.
>
> By the way, just in case this looks like a random request...
>
> A few merge conflicts between independent topic branches is not a big
> deal; we can deal with those.
>
> What's somewhat annoying though, is when a previous cleanup branch
> conflicts with later features. So, please base features on top of
> cleanups accordingly.
Hmm. And here I was thinking that I was basing branches on top of
each-other too much given your previous comments about merge conflicts
being OK!
In case it helps, the following commit in linux-next shows the conflict
resolution:
ee05948 Merge branch 'for-3.9/scu-base-rework' into for-3.9/soc-t114
I guess I missed this because I didn't merge for-3.9/scu-base-rework
into my for-next on its own, but only as part of for-3.9/soc-t114,
within which I had resolved the conflict as above.
So, you could just skip this pull request, and it'll be pulled in when
you merge for-3.9/soc-t114.
It that doesn't work for you, I can do the rebase tomorrow morning.
next prev parent reply other threads:[~2013-02-01 4:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 21:42 [GIT PULL 1/8] ARM: tegra: cleanup Stephen Warren
[not found] ` <1359582159-28816-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-30 21:42 ` [GIT PULL 2/8] ARM: tegra: Common Clock Framework rework Stephen Warren
2013-01-30 21:42 ` [GIT PULL 3/8] ARM: tegra: USB driver cleanup Stephen Warren
2013-01-30 21:42 ` [GIT PULL 4/8] ARM: tegra: cpuidle enhancements Stephen Warren
2013-01-30 21:42 ` [GIT PULL 5/8] ARM: tegra: SCU base rework Stephen Warren
[not found] ` <1359582159-28816-5-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-01 4:32 ` Olof Johansson
[not found] ` <20130201043222.GC5844-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2013-02-01 4:35 ` Olof Johansson
[not found] ` <CAOesGMjjgz7Am7-D_fQHqgLX=G+Wc_LKL-GYMHd1-NzVC-DUfA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-01 4:46 ` Stephen Warren [this message]
[not found] ` <510B4892.3050900-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-01 15:51 ` Arnd Bergmann
2013-01-30 21:42 ` [GIT PULL 6/8] ARM: tegra: add Tegra114 SoC support Stephen Warren
2013-01-30 21:42 ` [GIT PULL 7/8] ARM: tegra: device tree updates Stephen Warren
2013-01-30 21:42 ` [GIT PULL 8/8] ARM: tegra: defconfig update Stephen Warren
[not found] ` <1359582159-28816-8-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-05 21:26 ` Olof Johansson
[not found] ` <20130205212604.GA30719-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2013-02-06 0:26 ` Stephen Warren
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=510B4892.3050900@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.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