From: Peter Robinson <pbrobinson@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: pinctrl: adjust dependencies closer to arch/SoC
Date: Sun, 27 Dec 2015 12:22:50 +0000 [thread overview]
Message-ID: <1451218972-22156-1-git-send-email-pbrobinson@gmail.com> (raw)
Hi All,
In enabling just ARCH_ROCKCHIP, or a number of other combos, you get numerous other
non related pinctrl options that appear just by selecting PINCTRL. These two patches
add appropriate dependencies and COMPILE_TEST to allow finer grained control.
Peter
next reply other threads:[~2015-12-27 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 12:22 Peter Robinson [this message]
2015-12-27 12:22 ` [PATCH 1/2] pinctrl: intel: on enable on x86 arches and COMPILE_TEST Peter Robinson
2015-12-28 12:00 ` Mika Westerberg
2015-12-28 12:13 ` Peter Robinson
2015-12-28 12:37 ` Mika Westerberg
2015-12-27 12:22 ` [PATCH 2/2] pinctrl: AMD: depend on Seattle or x86 Peter Robinson
2016-01-05 14:58 ` 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=1451218972-22156-1-git-send-email-pbrobinson@gmail.com \
--to=pbrobinson@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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).