From: Randy Dunlap <rdunlap@infradead.org>
To: Kangmin Park <l4stpr0gr4m@gmail.com>, linux-kernel@vger.kernel.org
Cc: Jiri Kosina <trivial@kernel.org>
Subject: Re: Fix a typo in Documentation/sysctl/vm.txt
Date: Tue, 3 Oct 2017 08:01:33 -0700 [thread overview]
Message-ID: <df4c8b24-967c-7739-e3d8-c35fa48ae1fe@infradead.org> (raw)
In-Reply-To: <CAKW4uUzmf0EtHeUC8eDxqqSyHzonKyZAjUTBuqG-U8LiqN1bjA@mail.gmail.com>
On 10/03/17 00:56, Kangmin Park wrote:
> --- linux/Documentation/sysctl/vm.txt.orig 2017-09-07 00:19:43.260477784 +0900
> +++ linux/Documentation/sysctl/vm.txt 2017-09-07 00:19:56.498431846 +0900
> @@ -793,7 +793,7 @@ with no ill effects: errors and warnings
> swappiness
>
> This control is used to define how aggressive the kernel will swap
> -memory pages. Higher values will increase agressiveness, lower values
> +memory pages. Higher values will increase aggressiveness, lower values
> decrease the amount of swap. A value of 0 instructs the kernel not to
> initiate swap until the amount of free and file-backed pages is less
> than the high water mark in a zone.
>
> Fixes a spelling in documentation.
>
> Signed-off-by: Kangmin Park <l4stpr0gr4m@gmail.com>
>
Hi,
The spelling correction is good, but the format of the patch is almost
upside down. The patch description should be first, then the Signed-off-by:
line, and then the patch is last.
And then you need to send it to someone specific who can merge it.
This one should probably be sent: Jiri Kosina <trivial@kernel.org>
(unless he wants to take it now).
with a Subject line of something like:
[PATCH trivial] Fix a typo in Documentation/sysctl/vm.txt
Thanks,
--
~Randy
prev parent reply other threads:[~2017-10-03 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 7:56 Kangmin Park
2017-10-03 15:01 ` Randy Dunlap [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=df4c8b24-967c-7739-e3d8-c35fa48ae1fe@infradead.org \
--to=rdunlap@infradead.org \
--cc=l4stpr0gr4m@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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
all inboxes | Powered by JetHome®