From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Randy Dunlap'" <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Cc: "'Avri Altman'" <avri.altman@wdc.com>,
<linux-scsi@vger.kernel.org>,
"'James E.J. Bottomley'" <jejb@linux.ibm.com>,
"'Martin K. Petersen'" <martin.petersen@oracle.com>
Subject: RE: [PATCH -next] scsi: ufs: fix all Kconfig help text indentation
Date: Thu, 7 Jan 2021 06:53:49 +0530 [thread overview]
Message-ID: <052001d6e493$c1fb0fb0$45f12f10$@samsung.com> (raw)
In-Reply-To: <20210106205554.18082-1-rdunlap@infradead.org>
Hello Randy,
> -----Original Message-----
> From: Randy Dunlap <rdunlap@infradead.org>
> Sent: 07 January 2021 02:26
> To: linux-kernel@vger.kernel.org
> Cc: Randy Dunlap <rdunlap@infradead.org>; Alim Akhtar
> <alim.akhtar@samsung.com>; Avri Altman <avri.altman@wdc.com>; linux-
> scsi@vger.kernel.org; James E.J. Bottomley <jejb@linux.ibm.com>; Martin K.
> Petersen <martin.petersen@oracle.com>
> Subject: [PATCH -next] scsi: ufs: fix all Kconfig help text indentation
>
> Use consistent and expected indentation for all Kconfig text.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Alim Akhtar <alim.akhtar@samsung.com>
> Cc: Avri Altman <avri.altman@wdc.com>
> Cc: linux-scsi@vger.kernel.org
> Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>
> Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
> ---
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
next prev parent reply other threads:[~2021-01-07 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210106205857epcas5p31c8d9aee87cb459ef431b8e8c965bdfe@epcas5p3.samsung.com>
2021-01-06 20:55 ` [PATCH -next] scsi: ufs: fix all Kconfig help text indentation Randy Dunlap
2021-01-07 1:23 ` Alim Akhtar [this message]
2021-01-08 3:40 ` Martin K. Petersen
2021-01-13 5:48 ` Martin K. Petersen
2021-01-07 6:03 kernel test robot
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='052001d6e493$c1fb0fb0$45f12f10$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.