linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.org>,
	Wei Yang <richard.weiyang@gmail.com>,
	trivial@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/page_alloc: Trivial typo fix.
Date: Tue, 6 Jun 2017 11:07:43 +0800	[thread overview]
Message-ID: <20170606030743.GC2259@WeideMacBook-Pro.local> (raw)
In-Reply-To: <20170605152905.3bf55d05ecdb91224b460197@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

On Mon, Jun 05, 2017 at 03:29:05PM -0700, Andrew Morton wrote:
>On Mon, 5 Jun 2017 08:22:48 +0200 Michal Hocko <mhocko@kernel.org> wrote:
>
>> On Mon 05-06-17 09:43:50, Wei Yang wrote:
>> > Looks there is no word "blamo", and it should be "blame".
>> > 
>> > This patch just fix the typo.
>> 
>> Well, I do not think this is a typo. blamo has a slang meaning which I
>> believe was intentional.
>
>It should be "blammo".
>
>> Besides that, why would you want to fix this
>> anyway. Is this something that you would grep for?
>
>Yup.  I wouldn't object to an incidental fix if someone was altering
>something else nearby or as part of a file-wide "clean up comments"
>patch, but it doesn't seem worth an entire commit.

Sure, maybe I can keep this when I have other related patches. :-)

-- 
Wei Yang
Help you, Help me

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-06-06  3:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  1:43 [PATCH] mm/page_alloc: Trivial typo fix Wei Yang
2017-06-05  6:22 ` Michal Hocko
2017-06-05 22:29   ` Andrew Morton
2017-06-06  3:07     ` Wei Yang [this message]
2017-06-06  3:06   ` Wei Yang

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=20170606030743.GC2259@WeideMacBook-Pro.local \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@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;
as well as URLs for NNTP newsgroup(s).