From: Nitin Gupta <nitin.m.gupta@oracle.com>
To: David Miller <davem@davemloft.net>, paul.gortmaker@windriver.com
Cc: mike.kravetz@oracle.com, kirill.shutemov@linux.intel.com,
tom.hromatka@oracle.com, mhocko@suse.com, mingo@kernel.org,
babu.moger@oracle.com, bob.picco@oracle.com,
thomas.tai@oracle.com, pasha.tatashin@oracle.com,
atish.patra@oracle.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc64: Add 16GB hugepage support
Date: Wed, 24 May 2017 21:08:40 -0700 [thread overview]
Message-ID: <4c4d4881-9634-9e62-243a-ed0c350b8a39@oracle.com> (raw)
In-Reply-To: <20170524.234504.246686489551587317.davem@davemloft.net>
On 5/24/17 8:45 PM, David Miller wrote:
> From: Paul Gortmaker <paul.gortmaker@windriver.com>
> Date: Wed, 24 May 2017 23:34:42 -0400
>
>> [[PATCH] sparc64: Add 16GB hugepage support] On 24/05/2017 (Wed 17:29) Nitin Gupta wrote:
>>
>>> Orabug: 25362942
>>>
>>> Signed-off-by: Nitin Gupta <nitin.m.gupta@oracle.com>
>>
>> If this wasn't an accidental git send-email misfire, then there should
>> be a long log indicating the use case, the perforamnce increase, the
>> testing that was done, etc. etc.
>>
>> Normally I'd not notice but since I was Cc'd I figured it was worth a
>> mention -- for example the vendor ID above doesn't mean a thing to
>> all the rest of us, hence why I suspect it was a git send-email misfire;
>> sadly, I think we've all accidentally done that at least once....
>
> Agreed.
>
> No commit message whatsoever is basically unacceptable for something
> like this.
>
Ok, I will include usage, testing notes, performance numbers etc., in
v2 patch. Still, I do try to include "Orabug" for better tracking of
bugs internally; I hope that's okay.
Thanks,
Nitin
prev parent reply other threads:[~2017-05-25 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 0:29 Nitin Gupta
2017-05-25 3:34 ` Paul Gortmaker
2017-05-25 3:45 ` David Miller
2017-05-25 4:08 ` Nitin Gupta [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=4c4d4881-9634-9e62-243a-ed0c350b8a39@oracle.com \
--to=nitin.m.gupta@oracle.com \
--cc=atish.patra@oracle.com \
--cc=babu.moger@oracle.com \
--cc=bob.picco@oracle.com \
--cc=davem@davemloft.net \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=mingo@kernel.org \
--cc=pasha.tatashin@oracle.com \
--cc=paul.gortmaker@windriver.com \
--cc=sparclinux@vger.kernel.org \
--cc=thomas.tai@oracle.com \
--cc=tom.hromatka@oracle.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 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®