[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170524.234504.246686489551587317.davem@davemloft.net>
Date: Wed, 24 May 2017 23:45:04 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: paul.gortmaker@...driver.com
Cc: nitin.m.gupta@...cle.com, mike.kravetz@...cle.com,
kirill.shutemov@...ux.intel.com, tom.hromatka@...cle.com,
mhocko@...e.com, mingo@...nel.org, babu.moger@...cle.com,
bob.picco@...cle.com, thomas.tai@...cle.com,
pasha.tatashin@...cle.com, atish.patra@...cle.com,
sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sparc64: Add 16GB hugepage support
From: Paul Gortmaker <paul.gortmaker@...driver.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@...cle.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.
Powered by blists - more mailing lists