From: Jonathan Cameron <jic23@kernel.org>
To: William Breathitt Gray <vilhelm.gray@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH 0/3] pc104: Mask PC/104 Kconfig options
Date: Sun, 5 Mar 2017 12:48:47 +0000 [thread overview]
Message-ID: <61fd7559-9001-ede7-f16d-2f74f8f9ef61@kernel.org> (raw)
In-Reply-To: <20170301204652.GA31812@sophia>
On 01/03/17 20:46, William Breathitt Gray wrote:
> On Wed, Jan 11, 2017 at 04:26:19PM +0100, Linus Walleij wrote:
>> On Tue, Jan 10, 2017 at 7:50 PM, William Breathitt Gray
>> <vilhelm.gray@gmail.com> wrote:
>>
>>> 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.
>>
>> Tell me when/if the PC104 option is merged and I can merge the GPIO
>> patch.
>>
>> Yours,
>> Linus Walleij
>
> Jonathan and Linus,
>
> Now that the PC104 option is merged for 4.11, it should be all right to
> merge in the GPIO and IIO patches without worry of warnings. Please
> merge the relevant patch to your respective tree after you pull in the
> PC104 option.
If it looks like I've forgotten this, feel free to poke me again!
At least replying to you should get it back into my recent threads
in my email client ;)
Jonathan
>
> Thank you,
>
> William Breathitt Gray
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-03-05 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 18:50 [PATCH 0/3] pc104: Mask PC/104 Kconfig options William Breathitt Gray
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 [this message]
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=61fd7559-9001-ede7-f16d-2f74f8f9ef61@kernel.org \
--to=jic23@kernel.org \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.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 \
--cc=vilhelm.gray@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).