From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: gregkh@linuxfoundation.org
Cc: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linus.walleij@linaro.org, gnurou@gmail.com,
William Breathitt Gray <vilhelm.gray@gmail.com>
Subject: [PATCH 0/3] pc104: Mask PC/104 Kconfig options
Date: Tue, 10 Jan 2017 13:50:28 -0500 [thread overview]
Message-ID: <cover.1484073324.git.vilhelm.gray@gmail.com> (raw)
PC/104 form factor devices serve a specific niche of embedded system
users. Since PC/104 devices and hardware are typically used by just a
subset of Linux users, it would be appropriate to filter PC/104 related
Kconfig options for those uninterested.
This patchset introduces the PC104 Kconfig option, and uses it to mask
PC/104 specific device drivers and options, so that only those users
interested in PC/104 related Kconfig options are exposed to them.
William Breathitt Gray (3):
pc104: Introduce the PC104 Kconfig option
gpio: pc104: Mask PC/104 drivers via PC104 Kconfig option
iio: pc104: Mask PC/104 drivers via the PC104 Kconfig option
drivers/gpio/Kconfig | 8 ++++----
drivers/iio/adc/Kconfig | 2 +-
drivers/iio/counter/Kconfig | 2 +-
init/Kconfig | 7 +++++++
4 files changed, 13 insertions(+), 6 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-10 18:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 18:50 William Breathitt Gray [this message]
2017-01-10 18:50 ` [PATCH 1/3] pc104: Introduce the PC104 Kconfig option William Breathitt Gray
2017-01-10 18:51 ` [PATCH 2/3] gpio: pc104: Mask PC/104 drivers via " William Breathitt Gray
2017-03-14 15:25 ` Linus Walleij
2017-01-10 18:51 ` [PATCH 3/3] iio: pc104: Mask PC/104 drivers via the " William Breathitt Gray
2017-01-10 21:13 ` Jonathan Cameron
2017-01-10 21:45 ` William Breathitt Gray
2017-01-11 15:45 ` Linus Walleij
2017-01-19 11:42 ` Greg KH
2017-01-11 15:26 ` [PATCH 0/3] pc104: Mask PC/104 Kconfig options Linus Walleij
2017-03-01 20:46 ` William Breathitt Gray
2017-03-05 12:48 ` Jonathan Cameron
2017-03-15 22:00 ` Jonathan Cameron
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=cover.1484073324.git.vilhelm.gray@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).