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 22:57:23 +0100 [thread overview]
Message-ID: <5679C743.1070000@free.fr> (raw)
In-Reply-To: <7hoadi6wfw.fsf@deeprootsystems.com>
On 22/12/2015 21:49, Kevin Hilman wrote:
> Mason wrote:
>
>> On 22/12/2015 20:25, Kevin Hilman wrote:
>>
>>> 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?
>
> Not sure what you're asking.
>
> The point is that this series doesn't enable any defconfig to build it.
What is not clear to me is: are you asking me to submit a new defconfig
(specific to my platform), or are you saying I need to add the new
platform to arch/arm/configs/multi_v7_defconfig (I'm not sure how exactly
to go about doing that; also I'm concerned about merge conflicts, since
my patch set is based on v4.1)
>>> 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
>
> Which means it presumably wont boot without that, but it should still
> build without it, correct? (I tried it locally, and it does.)
Can I submit the defconfig update as a follow-up patch?
Regards.
next prev parent reply other threads:[~2015-12-22 21:57 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
2015-12-22 20:49 ` Kevin Hilman
2015-12-22 21:57 ` Mason [this message]
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=5679C743.1070000@free.fr \
--to=slash.tmp@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.