[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170619.235104.349838763068474531.davem@davemloft.net>
Date: Mon, 19 Jun 2017 23:51:04 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: nitin.m.gupta@...cle.com
Cc: mike.kravetz@...cle.com, kirill.shutemov@...ux.intel.com,
tom.hromatka@...cle.com, mhocko@...e.com, mingo@...nel.org,
hughd@...gle.com, bob.picco@...cle.com, pasha.tatashin@...cle.com,
steven.sistare@...cle.com, paul.gortmaker@...driver.com,
thomas.tai@...cle.com, atish.patra@...cle.com,
sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/4] sparc64: Add 16GB hugepage support
You need to provide a proper "[PATCH xxx 0/N] " header posting
explaining what the series is doing at a high level, how it is
doing it, and why it is doing it that way.
A patch series is a collection of related patches attempting to
achieve a specific high level end goal.
If, instead, these are just scattered unrelated changes, they do not
belong in a patch series and instead should be submitted individually.
Otherwise, if they belong together, you have to explain what that
grouping and purpose is in your header posting.
Thanks.
Powered by blists - more mailing lists