From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: soc changes for v3.13
Date: Wed, 09 Oct 2013 13:20:16 -0700 [thread overview]
Message-ID: <87txgqtcvz.fsf@linaro.org> (raw)
In-Reply-To: <20131008155440.GI5402@titan.lakedaemon.net> (Jason Cooper's message of "Tue, 8 Oct 2013 11:54:40 -0400")
Jason Cooper <jason@lakedaemon.net> writes:
> On Mon, Oct 07, 2013 at 10:06:40AM -0700, Olof Johansson wrote:
>> On Mon, Sep 30, 2013 at 11:42:08AM -0400, Jason Cooper wrote:
>> > Guys,
>> >
>> > These are the SoC changes that didn't make it during the last merge
>> > window. As with mvebu/drivers, these have been in -next since 3.12-rc1
>> > without issue.
>>
>> I should have looked closer at this before I commented on the PCI branch.
>>
>> > Sebastian Hesselbarth (2):
>> > ARM: dove: switch to DT probed mbus address windows
>> > ARM: dove: remove legacy pcie and clock init
>>
>> It looks to me like this second patch will need to be based on the PCI branch,
>> or you will have broken PCI if this is applied and not the drivers/pci patches,
>> right? If so, you need to base this branch on top of the other one, not send
>> them separately -- otherwise a git bisect that lands between these two will
>> result in a non-booting kernel.
>
> I've moved both patches over to mvebu/drivers. This leaves one patch in
> mvebu/soc. I'll hold off on the pull request for it until I have some
> more (looks like there's some stuff pending).
OK, ignoring the soc branch for now.
Kevin
prev parent reply other threads:[~2013-10-09 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 15:42 [GIT PULL] ARM: mvebu: soc changes for v3.13 Jason Cooper
2013-10-07 17:06 ` Olof Johansson
2013-10-07 18:13 ` Jason Cooper
2013-10-08 15:54 ` Jason Cooper
2013-10-09 20:20 ` Kevin Hilman [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=87txgqtcvz.fsf@linaro.org \
--to=khilman@linaro.org \
--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.