From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S941573AbdEYDpM (ORCPT <rfc822;w@1wt.eu>);
        Wed, 24 May 2017 23:45:12 -0400
Received: from shards.monkeyblade.net ([184.105.139.130]:53018 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S941523AbdEYDpJ (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 May 2017 23:45:09 -0400
Date: Wed, 24 May 2017 23:45:04 -0400 (EDT)
Message-Id: <20170524.234504.246686489551587317.davem@davemloft.net>
To: paul.gortmaker@windriver.com
Cc: nitin.m.gupta@oracle.com, 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
From: David Miller <davem@davemloft.net>
In-Reply-To: <20170525033442.GB877@windriver.com>
References: <1495672233-116815-1-git-send-email-nitin.m.gupta@oracle.com>
        <20170525033442.GB877@windriver.com>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Wed, 24 May 2017 20:03:34 -0700 (PDT)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.