From: Rahul Tanwar <rtanwar@maxlinear.com>
To: Randy Dunlap <rdunlap@infradead.org>, Pavel Machek <pavel@ucw.cz>
Cc: Arnd Bergmann <arnd@kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Adam Borowski <kilobyte@angband.pl>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
John Crispin <john@phrozen.org>,
Hauke Mehrtens <hmehrtens@maxlinear.com>,
Cheol Yong Kim <ckim@maxlinear.com>,
Qiming Wu <qwu@maxlinear.com>
Subject: Re: [PATCH 1/1] leds: lgm: Improve Kconfig help
Date: Thu, 18 Mar 2021 09:24:22 +0000 [thread overview]
Message-ID: <MN2PR19MB3693144BDCCAEF6F7FAB6BC0B1699@MN2PR19MB3693.namprd19.prod.outlook.com> (raw)
In-Reply-To: 42a0c810-4b6f-1853-60c9-e36a9dc6100a@infradead.org
Hi Randy,
On 18/3/2021 11:02 am, Randy Dunlap wrote:
> This email was sent from outside of MaxLinear.
>
>
> Hi,
>
> For the leds/blink/Kconfig file at least, something has
> changed all of the tabs to spaces.
>
> Keywords in Kconfig files should be indented with one tab,
> while help text should be indented with one tab + 2 spaces.
>
Hmm, facing some IT issues with git send-email so i had to send it by
other means. I will fix it in V1 by ensuring that i send using git.
>
> On 3/17/21 3:04 AM, Rahul Tanwar wrote:
>> Remove unnecessary Kconfig symbol LEDS_BLINK
>> Improve Kconfig help text to make it more useful.
>>
>> Signed-off-by: Rahul Tanwar <rtanwar@maxlinear.com>
>> ---
>>
>> diff --git a/drivers/leds/blink/Kconfig b/drivers/leds/blink/Kconfig
>> index 6dedc58c47b3..2de2973fbc6b 100644
>> --- a/drivers/leds/blink/Kconfig
>> +++ b/drivers/leds/blink/Kconfig
>> @@ -1,21 +1,19 @@
>> -menuconfig LEDS_BLINK
>> - bool "LED Blink support"
>> - depends on LEDS_CLASS
>> - help
>> - This option enables blink support for the leds class.
>> - If unsure, say Y.
>> -
>> -if LEDS_BLINK
>> -
>> -config LEDS_BLINK_LGM
>> - tristate "LED support for Intel LGM SoC series"
>> +config LEDS_LGM
>> + tristate "LED support for LGM SoC series"
>> depends on GPIOLIB
>> depends on LEDS_CLASS
>> depends on MFD_SYSCON
>> depends on OF
>> help
>> - Parallel to serial conversion, which is also called SSO
>> controller,
>> - can drive external shift register for LED outputs.
>> - This enables LED support for Serial Shift Output controller(SSO).
>> + This option enables support for LEDs connected to GPIO lines on
>> + Lightning Mountain(LGM) SoC. These LEDs are driven by a Serial
>
> Mountain (LGM)
>
>> + Shift Output(SSO) controller. The driver supports hardware
>
> Output (SSO)
>
>> + blinking with a configurable LED update/blink frequency in two
>> + modes, 2/4/8/10 Hz in low speed mode and 50/100/200/250 KHz in
>> + high speed mode. The LEDs can be configured to be triggered by
>> + SW/CPU or by hardware. Say 'Y' here if you are working on LGM
>
> Please spell out "software".
>
>> + SoC based platform.
>> +
>> + To compile this driver as a module, choose M here: the
>> + module will be called leds-lgm-sso.
>>
>> -endif # LEDS_BLINK
>
Well noted about above improvements suggestions. Shall update in V1. Thanks.
Regards,
Rahul
> thanks.
> --
> ~Randy
>
>
next prev parent reply other threads:[~2021-03-18 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8ae0456a08ef1a2491fd382b273ff7259e6fcbd0.1615969806.git.rtanwar@maxlinear.com>
2021-03-17 10:04 ` [PATCH 1/1] leds: lgm: Improve Kconfig help Rahul Tanwar
2021-03-18 1:54 ` Randy Dunlap
2021-03-18 9:24 ` Rahul Tanwar [this message]
2021-03-18 9:44 ` Arnd Bergmann
2021-03-18 7:55 ` Pavel Machek
2021-03-18 9:49 ` Rahul Tanwar
2021-03-18 20:37 ` Pavel Machek
2021-03-19 5:52 ` Rahul Tanwar
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=MN2PR19MB3693144BDCCAEF6F7FAB6BC0B1699@MN2PR19MB3693.namprd19.prod.outlook.com \
--to=rtanwar@maxlinear.com \
--cc=arnd@kernel.org \
--cc=ckim@maxlinear.com \
--cc=hmehrtens@maxlinear.com \
--cc=john@phrozen.org \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=qwu@maxlinear.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).