From: Paul Bolle <pebolle@tiscali.nl>
To: Ray Jui <rjui@broadcom.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>,
Christian Daudt <bcm@fixthebug.org>,
Matt Porter <mporter@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Scott Branden <sbranden@broadcom.com>,
Dmitry Torokhov <dtor@google.com>,
Anatol Pomazau <anatol@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 3/8] pinctrl: cygnus: add initial IOMUX driver support
Date: Mon, 09 Mar 2015 20:30:42 +0100 [thread overview]
Message-ID: <1425929442.2317.39.camel@tiscali.nl> (raw)
In-Reply-To: <54FDEDBA.1070404@broadcom.com>
Ray Jui schreef op ma 09-03-2015 om 12:00 [-0700]:
> I think it depends on how you see it. Based on this logic, then one can
> also argue comments in the code will be pre-processed away and are not
> needed. They at least serve the same documentation purpose in a way.
So why not make them comments? And even that might not be needed:
- MODULE_LICENSE() only summarizes, in just a few words, what takes a
few paragraphs in the customary comment at the top of a file;
- MODULE_DESCRIPTION() repeats what, in general, has been said in the
Kconfig entry for that driver and in the git commit explanation;
- and I'm not sure what the benefit is of MODULE_AUTHOR() in the first
place (even for actually modular drivers).
> So
> far I haven't seen other people complaining that having these module
> based macros in the driver are confusing when the Kconfig has a bool.
Perhaps that's just because review doesn't spot all issues. Patch
bandwidth exceeding review bandwidth and all that.
Anyhow, right now there's another thread discussing the questions my
review comments raise. Eg, "The Kconfig symbol is bool, there is module
related code in the driver, why note make the Kconfig symbol tristate
(and the driver modular)?". I think that is one of the questions mixing
built-in and modular semantics raises.
Paul Bolle
next prev parent reply other threads:[~2015-03-09 19:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 0:35 [PATCH v5 0/8] Add pinctrl support to Broadcom Cygnus SoC Ray Jui
2015-03-05 0:35 ` [PATCH v5 1/8] pinctrl: bcm: consolidate Broadcom pinctrl drivers Ray Jui
2015-03-09 16:20 ` Linus Walleij
2015-03-05 0:35 ` [PATCH v5 2/8] pinctrl: Broadcom Cygnus pinctrl device tree binding Ray Jui
2015-03-09 16:22 ` Linus Walleij
2015-03-05 0:35 ` [PATCH v5 3/8] pinctrl: cygnus: add initial IOMUX driver support Ray Jui
2015-03-05 8:03 ` Paul Bolle
2015-03-09 16:28 ` Linus Walleij
2015-03-09 18:40 ` Paul Bolle
2015-03-09 19:00 ` Ray Jui
2015-03-09 19:30 ` Paul Bolle [this message]
2015-03-09 19:40 ` Ray Jui
2015-03-09 19:53 ` Paul Bolle
2015-03-09 16:26 ` Linus Walleij
2015-03-05 0:35 ` [PATCH v5 4/8] ARM: dts: enable IOMUX for Broadcom Cygnus Ray Jui
2015-03-09 16:29 ` Linus Walleij
2015-03-05 0:35 ` [PATCH v5 5/8] pinctrl: Cygnus: define Broadcom Cygnus GPIO/PINCONF binding Ray Jui
2015-03-09 16:30 ` Linus Walleij
2015-03-09 16:41 ` Ray Jui
2015-03-05 0:35 ` [PATCH v5 6/8] pinctrl: cygnus: add gpio/pinconf driver Ray Jui
2015-03-05 8:11 ` Paul Bolle
2015-03-05 8:36 ` Paul Bolle
2015-03-05 17:13 ` Ray Jui
2015-03-09 16:41 ` Linus Walleij
2015-03-09 18:47 ` Paul Bolle
2015-03-05 0:35 ` [PATCH v5 7/8] ARM: dts: enable GPIO for Broadcom Cygnus Ray Jui
2015-03-05 0:35 ` [PATCH v5 8/8] ARM: dts: cygnus: enable GPIO based hook detection Ray Jui
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=1425929442.2317.39.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=anatol@google.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bcm@fixthebug.org \
--cc=devicetree@vger.kernel.org \
--cc=dtor@google.com \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mporter@linaro.org \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®