From: Paul Bolle <pebolle@tiscali.nl>
To: Leo Yan <leo.yan@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Wei Xu <xuwei5@hisilicon.com>,
Bintian Wang <bintian.wang@huawei.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Guodong Xu <guodong.xu@linaro.org>,
Jian Zhang <zhangjian001@hisilicon.com>,
Zhenwei Wang <Zhenwei.wang@hisilicon.com>,
Haoju Mo <mohaoju@hisilicon.com>,
Dan Zhao <dan.zhao@hisilicon.com>,
kongfei@hisilicon.com, Guangyue Zeng <zengguangyue@hisilicon.com>
Subject: Re: [RFC PATCH 2/3] mailbox: Hisilicon: add mailbox driver
Date: Tue, 04 Aug 2015 11:17:39 +0200 [thread overview]
Message-ID: <1438679859.8734.35.camel@tiscali.nl> (raw)
In-Reply-To: <20150804084930.GA27609@leoy-linaro>
On di, 2015-08-04 at 16:49 +0800, Leo Yan wrote:
> On Tue, Aug 04, 2015 at 10:30:24AM +0200, Paul Bolle wrote:
> > On ma, 2015-08-03 at 09:13 +0800, Leo Yan wrote:
> > > --- /dev/null
> > > +++ b/drivers/mailbox/hisilicon/Kconfig
> >
> > > +config HISI_MBOX
> > > + bool "Hisilicon's Mailbox"
> > > + depends on ARCH_HISI || OF
> >
> > ARCH_HISI is available on either ARM64 or ARM. ARM64 selects OF. On ARM
> > ARCH_HISI depends on ARCH_MULTIV7 which depends on ARCH_MULTIPLATFORM.
> > That selects USE_OF which on its turn selects OF.
> >
> > So, HISI_MBOX implies OF, correct?
>
> Exactly, will simply use "depends on ARCH_HISI".
That change would alter the dependencies. My remark was made just to
make clear why I think CONFIG_OF will always be defined. But now I guess
you actually meant
depends on ARCH_HISI && OF
And that would, I think, indeed be equivalent to
depends on ARCH_HISI
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-08-04 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 1:13 [RFC PATCH 0/3] mailbox: hisilicon: add mailbox driver Leo Yan
2015-08-03 1:13 ` [RFC PATCH 1/3] dt-bindings: mailbox: Document Hisilicon " Leo Yan
2015-08-03 1:13 ` [RFC PATCH 2/3] mailbox: Hisilicon: add " Leo Yan
2015-08-04 8:30 ` Paul Bolle
2015-08-04 8:49 ` Leo Yan
2015-08-04 9:00 ` Leo Yan
2015-08-04 9:17 ` Paul Bolle [this message]
2015-08-04 9:56 ` Leo Yan
2015-08-03 1:13 ` [RFC PATCH 3/3] arm64: dts: add Hi6220 mailbox node Leo Yan
2015-08-05 10:52 ` [RFC PATCH 0/3] mailbox: hisilicon: add mailbox driver Jassi Brar
2015-08-05 23:17 ` Leo Yan
2015-08-10 7:02 ` Jassi Brar
2015-08-10 8:52 ` Leo Yan
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=1438679859.8734.35.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=Zhenwei.wang@hisilicon.com \
--cc=bintian.wang@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=dan.zhao@hisilicon.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=guodong.xu@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jassisinghbrar@gmail.com \
--cc=kongfei@hisilicon.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mohaoju@hisilicon.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.com \
--cc=zengguangyue@hisilicon.com \
--cc=zhangjian001@hisilicon.com \
/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).