From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Support for Fujitsu MB86S7X SoCs
Date: Wed, 1 Apr 2015 17:50:53 -0700 [thread overview]
Message-ID: <20150402005053.GI8137@localhost> (raw)
In-Reply-To: <CAJe_ZheO1iNKj80798gT8RLcYoYo3xky3urw=ke4x-3wKdtZ9w@mail.gmail.com>
On Tue, Mar 31, 2015 at 08:32:01AM +0530, Jassi Brar wrote:
> On 18 March 2015 at 11:14, Vincent Yang <vincent.cw.yang@gmail.com> wrote:
> > Hi Arnd and Olof,
> >
> > Please consider pulling in these patches for series of Fujitsu SoC
> > based around variations of 2xCA7+2xCA15 big.LITTLE architecture.
> >
> > The MHU driver is already queued in Mailbox tree.
> >
> > Thanks,
> >
> > The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
> >
> > Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.linaro.org/landing-teams/working/fujitsu/integration.git
> > s7x-arch-pull
> >
> > for you to fetch changes up to 9cf417fee0bbea9296791fa9a15ab289307bb26a:
> >
> > ARM: MB86S7x: Add configs (2015-03-17 11:22:40 +0530)
> >
> > ----------------------------------------------------------------
> > Jassi Brar (6):
> > ARM: Add platform support for Fujitsu MB86S7X SoCs
> > ARM: MB86S7X: Add MCPM support
> > clk: Add clock driver for mb86s7x
> > dt: mb86s7x: add dt files for MB86S7x evbs
> > of: add Fujitsu vendor prefix
> > ARM: MB86S7x: Add configs
> >
> Hi Arnd, Hi Olof,
> A polite reminder on the pull request. Or do we miss doing something?
Hi,
No, we've just been backlogged and slow to respond.
-Olof
next prev parent reply other threads:[~2015-04-02 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 5:44 [GIT PULL] Support for Fujitsu MB86S7X SoCs Vincent Yang
2015-03-31 3:02 ` Jassi Brar
2015-04-02 0:50 ` Olof Johansson [this message]
2015-04-02 9:37 ` Sudeep Holla
2015-04-02 0:50 ` Olof Johansson
2015-04-07 8:14 ` Vincent Yang
2015-05-12 15:21 ` Arnd Bergmann
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=20150402005053.GI8137@localhost \
--to=olof@lixom.net \
--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).