linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentin Rothberg <valentinrothberg@gmail.com>
To: manabian@gmail.com
Cc: linus.walleij@linaro.org,
	Valentin Rothberg <valentinrothberg@gmail.com>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	gnurou@gmail.com, Paul Bolle <pebolle@tiscali.nl>,
	hengelein Stefan <stefan.hengelein@fau.de>,
	Andreas Ruprecht <andreas.ruprecht@fau.de>
Subject: lpc18xx: undefined Kconfig option ARCH_LPC18XX
Date: Wed, 6 May 2015 10:02:06 +0200	[thread overview]
Message-ID: <CAD3Xx4Kswf+9wbLfuhf=j1fk65QPVj4zmEW0tpUC=yGf56QH7w@mail.gmail.com> (raw)

Hi Joachim,

there are two of your commits [1, 2] in today's linux-next (i.e.,
next-20150506).  Both of them add Kconfig options that depend on
ARCH_LPC18XX, which is not defined in Kconfig, see:

+       depends on OF && (ARCH_LPC18XX || COMPILE_TEST)

Is there a patch queued somewhere to add ARCH_LPC18XX ?

I detected this issue with ./scripts/checkkconfigsymbols.py by diffing
yesterday's and todays' linux-next trees.

Kind regards,
 Valentin

[1] 13a43fd9e905 ("gpio: add lpc18xx gpio driver")
[2] 3aba09daf3d4 ("pinctrl: add lpc18xx pinctrl driver")

             reply	other threads:[~2015-05-06  8:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  8:02 Valentin Rothberg [this message]
2015-05-06  9:10 ` lpc18xx: undefined Kconfig option ARCH_LPC18XX Joachim Eastwood
2015-05-12 10:40 ` Linus Walleij
2015-05-12 10:48   ` Valentin Rothberg
2015-05-12 12:03     ` Linus Walleij
2015-05-12 12:06       ` Linus Walleij
2015-05-12 14:57       ` Valentin Rothberg
2015-05-13  8:44         ` Linus Walleij

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='CAD3Xx4Kswf+9wbLfuhf=j1fk65QPVj4zmEW0tpUC=yGf56QH7w@mail.gmail.com' \
    --to=valentinrothberg@gmail.com \
    --cc=andreas.ruprecht@fau.de \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manabian@gmail.com \
    --cc=pebolle@tiscali.nl \
    --cc=stefan.hengelein@fau.de \
    /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).