From: Paul Bolle <pebolle@tiscali.nl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jassi Brar <jaswinder.singh@linaro.org>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Andy Green <andy.green@linaro.org>,
Vincent Yang <Vincent.Yang@tw.fujitsu.com>,
Tetsuya Nuriya <nuriya.tetsuya@jp.fujitsu.com>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: gpio: ARCH_MB86S7X?
Date: Fri, 23 Jan 2015 12:08:00 +0100 [thread overview]
Message-ID: <1422011280.30730.34.camel@x220> (raw)
In-Reply-To: <CACRpkdbikHEU57nKDxKTm9fm8S4dTAnCcH_3Fh18JEfDrqL=vw@mail.gmail.com>
On Fri, 2015-01-23 at 11:55 +0100, Linus Walleij wrote:
> On Fri, Jan 23, 2015 at 11:34 AM, Jassi Brar <jaswinder.singh@linaro.org> wrote:
> > On 23 January 2015 at 15:51, Paul Bolle <pebolle@tiscali.nl> wrote:
>
> >> So, for what it's worth, that dependency appears to be not needed to
> >> build this driver.
> >>
> > Linus.W, what do you suggest? Just drop the dependency?
>
> Nah, not right now atleast. As there is a plan to get the platform
> in it will just cause trouble.
>
> What we can do is to say that it will be available also for
> CONFIG_COMPILE_TEST, so it gets built on the servers
> etc.
>
> depends on ARCH_MB86S7X || COMPILE_TEST
>
> But then you better test it a lot because then it will be
> compiled on X86_64 and such.
Whatever you do, I won't be bothering you again about this. Unless
ARCH_MB86S7X takes a long time to land, that is.
Paul Bolle
prev parent reply other threads:[~2015-01-23 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 10:21 gpio: ARCH_MB86S7X? Paul Bolle
2015-01-23 10:34 ` Jassi Brar
2015-01-23 10:55 ` Linus Walleij
2015-01-23 11:08 ` Paul Bolle [this message]
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=1422011280.30730.34.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=Vincent.Yang@tw.fujitsu.com \
--cc=andy.green@linaro.org \
--cc=gnurou@gmail.com \
--cc=jaswinder.singh@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuriya.tetsuya@jp.fujitsu.com \
--cc=valentinrothberg@gmail.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).