From: slash.tmp@free•fr (Mason)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v11 0/2] Sigma Designs Tango4 port
Date: Tue, 22 Dec 2015 21:23:59 +0100 [thread overview]
Message-ID: <5679B15F.80106@free.fr> (raw)
In-Reply-To: <7hr3iexp3e.fsf@deeprootsystems.com>
On 22/12/2015 20:25, Kevin Hilman wrote:
> Marc Gonzalez wrote:
>
>> Changes since v10:
>> Add aliases and chosen DT nodes
>> Use CPU_CLK and SYS_CLK symbolic names
>> MPCore private memory region DT node
>> select TANGO_IRQ instead of GENERIC_IRQ_CHIP
>>
>> Changes planned for a future patch series:
>> Have clkgen driver export CD2 for USB, and CD6 for SDIO
>
> Was it intentional to leave out a multi_v7_defconfig change so that this
> actually builds? Or was that planned for a future series?
How is a multi_v7_defconfig different from any old defconfig?
> IMO, it should be part of this series so it gets build tested as soon as
> it's merged.
The problem is that a mandatory driver is missing upstream
(interrupt controller).
http://thread.gmane.org/gmane.linux.kernel/2089470
> Otherwise, looking good to me.
>
> Reviewed-by: Kevin Hilman <khilman@linaro•org>
Woot! I already have the next patch series mostly ready, but I suppose
I should wait for this one to be accepted before submitting a new one.
Regards.
next prev parent reply other threads:[~2015-12-22 20:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 9:37 [PATCH v11 0/2] Sigma Designs Tango4 port Marc Gonzalez
2015-12-15 9:39 ` [PATCH v11 1/2] arm-soc: Import initial tango4 device tree Marc Gonzalez
2015-12-15 9:41 ` [PATCH v11 2/2] arm-soc: Add support for tango4 platforms Marc Gonzalez
2015-12-22 19:25 ` [PATCH v11 0/2] Sigma Designs Tango4 port Kevin Hilman
2015-12-22 20:23 ` Mason [this message]
2015-12-22 20:49 ` Kevin Hilman
2015-12-22 21:57 ` Mason
2015-12-22 22:31 ` Kevin Hilman
2015-12-22 23:58 ` Kevin Hilman
2015-12-23 14:23 ` Mason
2015-12-22 23:12 ` Olof Johansson
2015-12-23 14:35 ` Mason
2016-01-07 5:08 ` 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=5679B15F.80106@free.fr \
--to=slash.tmp@free$(echo .)fr \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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