From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Andreas Färber" <afaerber@suse.de>,
"Sven Van Asbroeck" <thesven73@gmail.com>,
svendev@arcx.com, robh+dt@kernel.org, linus.walleij@linaro.org,
lee.jones@linaro.org, mark.rutland@arm.com, treding@nvidia.com,
david@lechnology.com, noralf@tronnes.org, johan@kernel.org,
monstr@monstr.eu, michal.vokac@ysoft.com, arnd@arndb.de,
john.garry@huawei.com, geert+renesas@glider.be,
robin.murphy@arm.com, sebastien.bourdelin@savoirfairelinux.com,
icenowy@aosc.io, stuyoder@gmail.com, maxime.ripard@bootlin.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/6] fieldbus_dev: add Fieldbus Device subsystem.
Date: Tue, 22 Jan 2019 16:51:05 -0500 [thread overview]
Message-ID: <20190122215104.GI26416@windriver.com> (raw)
In-Reply-To: <20190122185246.GA922@kroah.com>
[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
next prev parent reply other threads:[~2019-01-22 21:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:21 [PATCH v7 0/6] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2019-01-22 15:21 ` [PATCH v7 1/6] fieldbus_dev: add Fieldbus Device subsystem Sven Van Asbroeck
2019-01-22 16:56 ` Paul Gortmaker
2019-01-22 17:12 ` Andreas Färber
2019-01-22 18:52 ` Greg KH
2019-01-22 21:51 ` Paul Gortmaker [this message]
2019-01-24 18:07 ` Sven Van Asbroeck
2019-01-24 18:25 ` Greg KH
2019-03-01 13:35 ` Pavel Machek
2019-03-01 13:34 ` Pavel Machek
2019-03-01 14:24 ` Greg KH
2019-01-22 15:21 ` [PATCH v7 2/6] anybus-s: support HMS Anybus-S bus Sven Van Asbroeck
2019-01-22 15:21 ` [PATCH v7 3/6] anybus-s: support the Arcx anybus controller Sven Van Asbroeck
2019-01-22 15:21 ` [PATCH v7 4/6] dt-bindings: anybus-controller: document devicetree binding Sven Van Asbroeck
2019-01-22 15:21 ` [PATCH v7 5/6] dt-bindings: Add vendor prefix for arcx / Archronix Sven Van Asbroeck
2019-01-22 15:21 ` [PATCH v7 6/6] fieldbus_dev: support HMS Profinet IRT industrial controller Sven Van Asbroeck
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=20190122215104.GI26416@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=david@lechnology.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=icenowy@aosc.io \
--cc=johan@kernel.org \
--cc=john.garry@huawei.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=michal.vokac@ysoft.com \
--cc=monstr@monstr.eu \
--cc=noralf@tronnes.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sebastien.bourdelin@savoirfairelinux.com \
--cc=stuyoder@gmail.com \
--cc=svendev@arcx.com \
--cc=thesven73@gmail.com \
--cc=treding@nvidia.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