mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nitin.m.gupta@oracle.com
Cc: mike.kravetz@oracle.com, kirill.shutemov@linux.intel.com,
	tom.hromatka@oracle.com, mhocko@suse.com, mingo@kernel.org,
	hughd@google.com, bob.picco@oracle.com,
	pasha.tatashin@oracle.com, steven.sistare@oracle.com,
	paul.gortmaker@windriver.com, thomas.tai@oracle.com,
	atish.patra@oracle.com, sparclinux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] sparc64: Add 16GB hugepage support
Date: Mon, 19 Jun 2017 23:51:04 -0400 (EDT)	[thread overview]
Message-ID: <20170619.235104.349838763068474531.davem@davemloft.net> (raw)
In-Reply-To: <1497923621-96708-1-git-send-email-nitin.m.gupta@oracle.com>


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.

      parent reply	other threads:[~2017-06-20  3:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20  1:52 Nitin Gupta
2017-06-20  1:52 ` [PATCH v3 2/4] sparc64: Support huge PUD case in get_user_pages Nitin Gupta
2017-06-20  1:53 ` [PATCH v3 3/4] sparc64: Fix gup_huge_pmd Nitin Gupta
2017-06-20  1:53 ` [PATCH v3 4/4] sparc64: Cleanup hugepage table walk functions Nitin Gupta
2017-06-20  3:51 ` David Miller [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=20170619.235104.349838763068474531.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=atish.patra@oracle.com \
    --cc=bob.picco@oracle.com \
    --cc=hughd@google.com \
    --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=nitin.m.gupta@oracle.com \
    --cc=pasha.tatashin@oracle.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=steven.sistare@oracle.com \
    --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®