From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Prasad Pandit <ppandit@redhat.com>
Cc: Derek Kiernan <derek.kiernan@amd.com>,
Dragan Cvetic <dragan.cvetic@amd.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH v1] misc: sgi_gru: indent SGI_GRU option help text
Date: Fri, 12 Apr 2024 07:09:27 +0200 [thread overview]
Message-ID: <2024041235-seizing-thirty-6ce9@gregkh> (raw)
In-Reply-To: <20240412050502.65326-1-ppandit@redhat.com>
On Fri, Apr 12, 2024 at 10:35:02AM +0530, Prasad Pandit wrote:
> From: Prasad Pandit <pjp@fedoraproject.org>
>
> Fix indentation of SGI_GRU option's help text by adding
> leading spaces. Generally help text is indented by couple
> of spaces more beyond the leading tab <\t> character.
> It helps Kconfig parsers to read file without error.
>
> Signed-off-by: Prasad Pandit <pjp@fedoraproject.org>
> ---
> drivers/misc/Kconfig | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> v1:
> - s/\t/ / at line #431
> - CC public mailing list
v1 was the private version you sent, this is v2, right?
>
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index 4fb291f0bf7c..a6565c42a7b9 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -293,21 +293,21 @@ config SGI_GRU
> depends on X86_UV && SMP
> select MMU_NOTIFIER
> help
> - The GRU is a hardware resource located in the system chipset. The GRU
> - contains memory that can be mmapped into the user address space. This memory is
> - used to communicate with the GRU to perform functions such as load/store,
> - scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
> - instructions using user virtual addresses. GRU instructions (ex., bcopy) use
> - user virtual addresses for operands.
> + The GRU is a hardware resource located in the system chipset. The GRU
> + contains memory that can be mmapped into the user address space.
> + This memory is used to communicate with the GRU to perform functions
> + such as load/store, scatter/gather, bcopy, AMOs, etc. The GRU is
> + directly accessed by user instructions using user virtual addresses.
> + GRU instructions (ex., bcopy) use user virtual addresses for operands.
>
> - If you are not running on a SGI UV system, say N.
> + If you are not running on a SGI UV system, say N.
>
> config SGI_GRU_DEBUG
> bool "SGI GRU driver debug"
> depends on SGI_GRU
> help
> - This option enables additional debugging code for the SGI GRU driver.
> - If you are unsure, say N.
> + This option enables additional debugging code for the SGI GRU driver.
> + If you are unsure, say N.
>
> config APDS9802ALS
> tristate "Medfield Avago APDS9802 ALS Sensor module"
> @@ -428,7 +428,7 @@ config LATTICE_ECP3_CONFIG
> tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
> depends on SPI && SYSFS
> select FW_LOADER
> - default n
> + default n
This line should just be deleted in a separate patch as it is the
default.
Can you do this as a patch series for v3 please?
thanks,
greg k-h
next prev parent reply other threads:[~2024-04-12 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 5:05 [PATCH v1] misc: sgi_gru: indent SGI_GRU option help text Prasad Pandit
2024-04-12 5:09 ` Greg Kroah-Hartman [this message]
2024-04-12 5:22 ` Prasad Pandit
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=2024041235-seizing-thirty-6ce9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=derek.kiernan@amd.com \
--cc=dragan.cvetic@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.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 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.