lkml.org 
[lkml]   [2019]   [Jan]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v7 1/6] fieldbus_dev: add Fieldbus Device subsystem.
[Re: [PATCH v7 1/6] fieldbus_dev: add Fieldbus Device subsystem.] On 22/01/2019 (Tue 19:52) Greg KH wrote:

> On Tue, Jan 22, 2019 at 06:12:31PM +0100, Andreas Färber wrote:
> > Am 22.01.19 um 17:56 schrieb Paul Gortmaker:
> > > [[PATCH v7 1/6] fieldbus_dev: add Fieldbus Device subsystem.] On 22/01/2019 (Tue 10:21) Sven Van Asbroeck wrote:

[...]

> > >> diff --git a/drivers/fieldbus/Kconfig b/drivers/fieldbus/Kconfig
> > >> new file mode 100644
> > >> index 000000000000..5c2bef950d04
> > >> --- /dev/null
> > >> +++ b/drivers/fieldbus/Kconfig
> > >> @@ -0,0 +1,19 @@
> > >> +menuconfig FIELDBUS_DEV
> > >> + bool "Fieldbus Device Support"
> > >
> > > OK, so the core support is NOT tristate, ie not modular,
> >
> > Is that intentional though, and if so, why?
> >
> > If possible, I would much rather see it changed to tristate and leave
> > all the metadata below.

[...]

> And I thought when I made the comment about this code being a module,
> that would be the change, not this one forcing it not to be :(

Apologies Greg, I didn't see that earlier comment.

Conversion to tristate is of course perfectly fine as well; I'm just
against the inconsistency and addition of unused code. But tristate
solves both, and I usually mention that (but not this time...<sigh>)

I just default to suggesting removing the unused stuff, since it doesn't
change the runtime or implicitly expand the use case beyond what the
original author(s) intended. Many times (just as here with fieldbus)
I just don't know enough about it to say whether modular has a use case.

Paul.
--

>
> thanks,
>
> greg k-h

\
 
 \ /
  Last update: 2019-01-22 22:52    [W:0.135 / U:0.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site