linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Jassi Brar <jaswinder.singh@linaro.org>
Cc: 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>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: gpio: ARCH_MB86S7X?
Date: Fri, 23 Jan 2015 11:21:41 +0100	[thread overview]
Message-ID: <1422008501.30730.22.camel@x220> (raw)

Jassi,

Your commit 0da094d82c27 ("gpio: Add Fujitsu MB86S7x GPIO driver") is
included in today's linux-next (ie, next-20150123). I noticed because a
script I use to check linux-next spotted a problem in it.

That commit added the Kconfig symbol GPIO_MB86S7X and made it depend on
ARCH_MB86S7X. But there's no Kconfig symbol ARCH_MB86S7X in linux-next.
I assume a patch to add that symbol is queued somewhere. Is that
correct?

Please note that I actually managed to cross-compile
drivers/gpio/gpio-mb86s7x.c with this command:
    make ARCH=arm CROSS_COMPILE=arm-linux-gnu- EXTRA_CFLAGS="-DCONFIG_GPIOLIB=y" drivers/gpio/gpio-mb86s7x.o

So, for what it's worth, that dependency appears to be not needed to
build this driver.

Thanks,


Paul Bolle


             reply	other threads:[~2015-01-23 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 10:21 Paul Bolle [this message]
2015-01-23 10:34 ` gpio: ARCH_MB86S7X? Jassi Brar
2015-01-23 10:55   ` Linus Walleij
2015-01-23 11:08     ` Paul Bolle

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=1422008501.30730.22.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).