From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Support for Fujitsu MB86S7X SoCs
Date: Thu, 02 Apr 2015 10:37:47 +0100 [thread overview]
Message-ID: <551D0DEB.1060609@arm.com> (raw)
In-Reply-To: <CAJe_ZheO1iNKj80798gT8RLcYoYo3xky3urw=ke4x-3wKdtZ9w@mail.gmail.com>
On 31/03/15 04:02, 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.
>>
I see this in next but would like to fix the binding before it gets
merged in v4.1. I have provided feedback on that patch. Mainly the
compatible, clocks and the interrupt names have to fixed in the binding.
Code changes can be done later, but bindings no. I prefer an ACK from DT
guys if possible.
Regards,
Sudeep
next prev parent reply other threads:[~2015-04-02 9:37 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
2015-04-02 9:37 ` Sudeep Holla [this message]
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=551D0DEB.1060609@arm.com \
--to=sudeep.holla@arm.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).