From: Randy Dunlap <rdunlap@infradead.org>
To: Mateusz Holenko <mholenko@antmicro.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
devicetree@vger.kernel.org, linux-serial@vger.kernel.org
Cc: Stafford Horne <shorne@gmail.com>,
Karol Gugala <kgugala@antmicro.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Filip Kokosinski <fkokosinski@antmicro.com>,
Pawel Czarnecki <pczarnecki@internships.antmicro.com>,
Joel Stanley <joel@jms.id.au>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Maxime Ripard <mripard@kernel.org>,
Shawn Guo <shawnguo@kernel.org>, Heiko Stuebner <heiko@sntech.de>,
Sam Ravnborg <sam@ravnborg.org>, Icenowy Zheng <icenowy@aosc.io>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/5] drivers/soc/litex: add LiteX SoC Controller driver
Date: Tue, 25 Feb 2020 08:15:57 -0800 [thread overview]
Message-ID: <291b0a18-2b50-515e-d6f8-31f766dbe567@infradead.org> (raw)
In-Reply-To: <20200225094437.4170502-3-mholenko@antmicro.com>
On 2/25/20 12:46 AM, Mateusz Holenko wrote:
> diff --git a/drivers/soc/litex/Kconfig b/drivers/soc/litex/Kconfig
> new file mode 100644
> index 000000000000..22c78cda0b83
> --- /dev/null
> +++ b/drivers/soc/litex/Kconfig
> @@ -0,0 +1,14 @@
> +# SPDX-License_Identifier: GPL-2.0
> +
> +menu "Enable LiteX SoC Builder specific drivers"
> +
> +config LITEX_SOC_CONTROLLER
> + tristate "Enable LiteX SoC Controller driver"
> + help
> + This option enables the SoC Controller Driver which verifies
> + LiteX CSR access and provides common litex_get_reg/litex_set_reg
> + accessors.
> + All drivers that use functions from litex.h must depend on
> + LITEX_SOC_CONTROLLER
Hi,
Please indent the help text with 2 additional spaces, as explained in the
coding-style.rst file:
10) Kconfig configuration files
-------------------------------
For all of the Kconfig* configuration files throughout the source tree,
the indentation is somewhat different. Lines under a ``config`` definition
are indented with one tab, while help text is indented an additional two
spaces. Example::
config AUDIT
bool "Auditing support"
depends on NET
help
Enable auditing infrastructure that can be used with another
kernel subsystem, such as SELinux (which requires this for
logging of avc messages output). Does not do system-call
auditing without CONFIG_AUDITSYSCALL.
> +
> +endmenu
and then end the last line of the help text with a period ('.').
thanks.
--
~Randy
next prev parent reply other threads:[~2020-02-25 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 8:46 [PATCH v3 0/5] LiteX SoC controller and LiteUART serial driver Mateusz Holenko
2020-02-25 8:46 ` [PATCH v3 1/5] dt-bindings: vendor: add vendor prefix for LiteX Mateusz Holenko
2020-02-25 8:46 ` [PATCH v3 2/5] dt-bindings: soc: document LiteX SoC Controller bindings Mateusz Holenko
2020-02-25 9:10 ` Maxime Ripard
2020-03-17 8:29 ` Mateusz Holenko
2020-02-25 16:57 ` Rob Herring
2020-03-17 8:32 ` Mateusz Holenko
2020-02-25 8:46 ` [PATCH v3 3/5] drivers/soc/litex: add LiteX SoC Controller driver Mateusz Holenko
2020-02-25 9:25 ` Maxime Ripard
2020-03-17 9:44 ` Mateusz Holenko
2020-02-25 16:15 ` Randy Dunlap [this message]
2020-03-17 8:26 ` Mateusz Holenko
2020-02-25 8:47 ` [PATCH v3 4/5] dt-bindings: serial: document LiteUART bindings Mateusz Holenko
2020-02-25 8:47 ` [PATCH v3 5/5] drivers/tty/serial: add LiteUART driver Mateusz Holenko
2020-02-25 9:49 ` Mateusz Holenko
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=291b0a18-2b50-515e-d6f8-31f766dbe567@infradead.org \
--to=rdunlap@infradead.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fkokosinski@antmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=icenowy@aosc.io \
--cc=joel@jms.id.au \
--cc=jslaby@suse.com \
--cc=kgugala@antmicro.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mholenko@antmicro.com \
--cc=mripard@kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=pczarnecki@internships.antmicro.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=shawnguo@kernel.org \
--cc=shorne@gmail.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;
as well as URLs for NNTP newsgroup(s).