From: David Hildenbrand <david@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: fix trivial help text punctuation
Date: Mon, 2 Dec 2019 10:30:46 +0100 [thread overview]
Message-ID: <f98d7458-80d5-64da-6415-c9ffd7e436b9@redhat.com> (raw)
In-Reply-To: <c17f2c75-dc2a-42a4-2229-bb6b489addf2@infradead.org>
On 30.11.19 20:48, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> End a Kconfig help text sentence with a period (aka full stop).
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> mm/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- lnx-54.orig/mm/Kconfig
> +++ lnx-54/mm/Kconfig
> @@ -29,7 +29,7 @@ config FLATMEM_MANUAL
>
> For systems that have holes in their physical address
> spaces and for features like NUMA and memory hotplug,
> - choose "Sparse Memory"
> + choose "Sparse Memory".
>
> If unsure, choose this option (Flat Memory) over any other.
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2019-12-02 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 19:48 [PATCH] mm: fix trivial help text punctuation Randy Dunlap
2019-12-02 9:30 ` David Hildenbrand [this message]
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=f98d7458-80d5-64da-6415-c9ffd7e436b9@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--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).