From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL V2 1/4] mvebu driver changes for v3.10
Date: Fri, 19 Apr 2013 16:34:38 +0200 [thread overview]
Message-ID: <517155FE.30406@free-electrons.com> (raw)
In-Reply-To: <CAOesGMjD-VAZW-zL-jm65xSJkFLpzbYOdvN6-5pV1OW_vJDCWg@mail.gmail.com>
On 04/19/2013 04:09 PM, Olof Johansson wrote:
> On Wed, Apr 17, 2013 at 10:30 PM, Olof Johansson <olof@lixom.net> wrote:
>> On Tue, Apr 16, 2013 at 11:04:16AM -0400, Jason Cooper wrote:
>>>
>>> The following changes since commit 8bb9660418e05bb1845ac1a2428444d78e322cc7:
>>>
>>> Linux 3.9-rc4 (2013-03-23 16:52:44 -0700)
>>>
>>> are available in the git repository at:
>>>
>>> git://git.infradead.org/users/jcooper/linux.git tags/drivers-3.10-2
>>>
>>> for you to fetch changes up to ac7b07ec369324063e52c37b3fb0ad1a1814d879:
>>>
>>> clk: mvebu: add more PCIe clocks for Armada XP (2013-04-16 14:47:01 +0000)
>>
>> Pulled, thanks.
>
> Dropped due to build errors on powerpc64. 3.11 material now.
>
Wait! That means dropping _all_ the change done in mvebu for 3.10 just
for one patch in the of/pci part?
Jason, did you take the accurate patch? Because according to Grant
Likely, the build didn't fail on ppc, see:
http://www.spinics.net/lists/arm-kernel/msg238517.html
>
> -Olof
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-19 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 18:28 [GIT PULL 1/4] mvebu driver changes for v3.10 Jason Cooper
2013-04-16 15:04 ` [GIT PULL V2 " Jason Cooper
2013-04-18 5:30 ` Olof Johansson
2013-04-19 14:09 ` Olof Johansson
2013-04-19 14:34 ` Gregory CLEMENT [this message]
2013-04-19 16:12 ` Gregory CLEMENT
2013-04-19 17:15 ` Andrew Murray
2013-04-19 17:21 ` [GIT PULL V3 " Jason Cooper
2013-04-19 17:24 ` Olof Johansson
2013-04-19 17:41 ` Gregory CLEMENT
2013-04-19 17:50 ` Olof Johansson
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=517155FE.30406@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--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).