From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: SoC changes for v3.17
Date: Mon, 30 Jun 2014 14:11:02 +0200 [thread overview]
Message-ID: <20140630141102.44461793@free-electrons.com> (raw)
In-Reply-To: <20140630120652.GN23978@titan.lakedaemon.net>
Dear Jason Cooper,
On Mon, 30 Jun 2014 08:06:52 -0400, Jason Cooper wrote:
> On Mon, Jun 30, 2014 at 11:29:55AM +0100, Russell King - ARM Linux wrote:
> > On Mon, Jun 30, 2014 at 12:22:16PM +0200, Thomas Petazzoni wrote:
> > > Now that Russell is pushing PATCH 1/3 in the 3.16-rc cycle, can you
> > > push PATCH 2/3 and PATCH 3/3 pointed above into the 3.16-rc cycle as
> > > well?
> >
> > It's in -rc3.
>
> Do you want me to do a topic branch on top of -rc3 for these or can I
> just throw them on mvebu/fixes? iow, is there a dep?
There's no build dependency with the patch pushed by Russell. The patch
that went through Russell merely adds the support for a new DT property
in the PL310 DT binding, and the two patches that should go through
your tree use this new DT property. So there is really no build
dependency between the two things.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-30 12:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 12:46 [GIT PULL] ARM: mvebu: SoC changes for v3.17 Jason Cooper
2014-06-28 14:23 ` Thomas Petazzoni
2014-06-28 15:07 ` Jason Cooper
2014-06-28 15:20 ` Thomas Petazzoni
2014-06-29 9:35 ` Russell King - ARM Linux
2014-06-29 9:56 ` Thomas Petazzoni
2014-06-30 10:22 ` Thomas Petazzoni
2014-06-30 10:29 ` Russell King - ARM Linux
2014-06-30 12:06 ` Jason Cooper
2014-06-30 12:11 ` Thomas Petazzoni [this message]
2014-06-30 12:14 ` Jason Cooper
2014-06-30 17:44 ` Jason Cooper
2014-06-30 18:50 ` Thomas Petazzoni
2014-07-01 12:11 ` [GIT PULL V2] " Jason Cooper
2014-07-08 5:28 ` 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=20140630141102.44461793@free-electrons.com \
--to=thomas.petazzoni@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