[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170119114201.GA31804@kroah.com>
Date: Thu, 19 Jan 2017 12:42:01 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: William Breathitt Gray <vilhelm.gray@...il.com>,
Jonathan Cameron <jic23@...nel.org>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald <pmeerw@...erw.net>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Alexandre Courbot <gnurou@...il.com>
Subject: Re: [PATCH 3/3] iio: pc104: Mask PC/104 drivers via the PC104
Kconfig option
On Wed, Jan 11, 2017 at 04:45:26PM +0100, Linus Walleij wrote:
> On Tue, Jan 10, 2017 at 10:45 PM, William Breathitt Gray
> <vilhelm.gray@...il.com> wrote:
> > 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@...nel.org>
> >>> Cc: Hartmut Knaack <knaack.h@....de>
> >>> Cc: Lars-Peter Clausen <lars@...afoo.de>
> >>> Cc: Peter Meerwald-Stadler <pmeerw@...erw.net>
> >>> Signed-off-by: William Breathitt Gray <vilhelm.gray@...il.com>
> >>Acked-by: Jonathan Cameron <jic23@...nel.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.
>
> As long as Greg merges the first patch we can merge the two
> others orthogonally I think.
>
> It's just Kconfig symbols, not things that break compile.
>
> (But I bet someone will come with automated warnings about
> unused symbols in the kernel...)
We already have that tool, scripts/checkkconfigsymbols.pl :)
I'll go merge this first patch now.
thanks,
greg k-h
Powered by blists - more mailing lists