From: Arnd Bergmann <arnd@kernel.org>
To: Rahul Tanwar <rtanwar@maxlinear.com>
Cc: Randy Dunlap <rdunlap@infradead.org>, Pavel Machek <pavel@ucw.cz>,
"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 10:44:24 +0100 [thread overview]
Message-ID: <CAK8P3a3PjdgVDbH-cK7DygPYwZ85APQLCNHSOBtsCvybbmJ6fg@mail.gmail.com> (raw)
In-Reply-To: <MN2PR19MB3693144BDCCAEF6F7FAB6BC0B1699@MN2PR19MB3693.namprd19.prod.outlook.com>
On Thu, Mar 18, 2021 at 10:24 AM Rahul Tanwar <rtanwar@maxlinear.com> wrote:
>
> 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.
FYI, the usual convention is that 'v1' is the implied version when you
send a patch series for the first time. If you send an updated version,
you start counting at 'v2'.
Arnd
next prev parent reply other threads:[~2021-03-18 9:45 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
2021-03-18 9:44 ` Arnd Bergmann [this message]
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=CAK8P3a3PjdgVDbH-cK7DygPYwZ85APQLCNHSOBtsCvybbmJ6fg@mail.gmail.com \
--to=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 \
--cc=rtanwar@maxlinear.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).