From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Olof Johansson <olof@lixom.net>,
Andre Przywara <andre.przywara@arm.com>,
"arm@kernel.org" <arm@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64/sunxi: 4.6-rc1: Add dependency on generic irq chip
Date: Wed, 13 Apr 2016 14:20:37 +0100 [thread overview]
Message-ID: <570E47A5.3060807@arm.com> (raw)
In-Reply-To: <CAL_Jsq+_2byE=Bd7cs_ULCnsWobKW3QQ+6XE8LVEqmu=R-ur8A@mail.gmail.com>
On 13/04/16 14:17, Rob Herring wrote:
> On Wed, Apr 13, 2016 at 4:05 AM, Suzuki K Poulose
> <Suzuki.Poulose@arm.com> wrote:
>> On 12/04/16 20:11, Olof Johansson wrote:
>>>
>>> On Tue, Mar 29, 2016 at 11:03:06AM +0100, Suzuki K Poulose wrote:
>> Do you mean something like :
>> config ARCH_SUNXI
>> ...
>> select SUNXI_PLATFORM
>>
>> And have
>>
>> config SUNXI_PLATFORM
>> select SUNXI_DEPENDENCY_1
>> select SUNXI_DEPENDENCY_2
>>
>> where SUNXI_PLATFORM drives the dependencies for both ARM and ARM64 ?
>
> No, I believe what Olof is saying is make the kconfig symbol for the
> irqchip (irq-sunxi-nmi) select it. If there is not a kconfig symbol
> already for it because you just use ARCH_SUNXI directly, then add it.
Ok, makes sense. Thanks, will respin it.
Suzuki
next prev parent reply other threads:[~2016-04-13 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 10:03 [PATCH] arm64/sunxi: 4.6-rc1: Add dependency on generic irq chip Suzuki K Poulose
2016-04-06 9:05 ` Andre Przywara
2016-04-07 14:18 ` Suzuki K Poulose
2016-04-12 19:11 ` Olof Johansson
2016-04-13 9:05 ` Suzuki K Poulose
2016-04-13 13:17 ` Rob Herring
2016-04-13 13:20 ` Suzuki K Poulose [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-09 22:37 Andre Przywara
2016-05-10 19:10 ` Maxime Ripard
2016-05-10 19:44 ` 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=570E47A5.3060807@arm.com \
--to=suzuki.poulose@arm.com \
--cc=andre.przywara@arm.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh@kernel.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