linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
	knaack.h-Mmb7MZpHnFY@public.gmane.org,
	lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org,
	pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org,
	linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
	gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH 3/3] iio: pc104: Mask PC/104 drivers via the PC104 Kconfig option
Date: Tue, 10 Jan 2017 16:45:35 -0500	[thread overview]
Message-ID: <20170110214535.GA21354@sophia> (raw)
In-Reply-To: <4236ccf5-1480-ea3c-fee6-35ea252e3756-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

On Tue, Jan 10, 2017 at 09:13:02PM +0000, Jonathan Cameron wrote:
>On 10/01/17 18:51, William Breathitt Gray wrote:
>> PC/104 drivers should be hidden on machines which do not support PC/104
>> devices. This patch adds the PC104 Kconfig option as a dependency for
>> the relevant PC/104 device driver Kconfig options.
>> 
>> Cc: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>> Cc: Hartmut Knaack <knaack.h-Mmb7MZpHnFY@public.gmane.org>
>> Cc: Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
>> Cc: Peter Meerwald-Stadler <pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>
>> Signed-off-by: William Breathitt Gray <vilhelm.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>Acked-by: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>
>Now the question is how to merge this one.  Let me know if you
>want me to take this one via IIO after the first patch is in.
>If you want to take it another route I'm fine with that.
>
>Jonathan

This is such a simple patchset that I envision Greg K-H picking up all
three patches via driver-core; however, I'm pretty indifferent about the
ultimate path in the end. I'll leave it up to Greg K-H to decide.

William Breathitt Gray

  parent reply	other threads:[~2017-01-10 21:45 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
     [not found] ` <cover.1484073324.git.vilhelm.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
     [not found]       ` <4236ccf5-1480-ea3c-fee6-35ea252e3756-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-10 21:45         ` William Breathitt Gray [this message]
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
     [not found]       ` <61fd7559-9001-ede7-f16d-2f74f8f9ef61-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
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=20170110214535.GA21354@sophia \
    --to=vilhelm.gray-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=knaack.h-Mmb7MZpHnFY@public.gmane.org \
    --cc=lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org \
    --cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org \
    /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).