From: Andrew Morton <akpm@linux-foundation.org>
To: "Pearson, Greg" <greg.pearson@hp.com>
Cc: Tejun Heo <tj@kernel.org>,
"hpa@linux.intel.com" <hpa@linux.intel.com>,
"shangw@linux.vnet.ibm.com" <shangw@linux.vnet.ibm.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"yinghai@kernel.org" <yinghai@kernel.org>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] mm/memblock: fix overlapping allocation when doubling reserved array
Date: Tue, 19 Jun 2012 15:21:47 -0700 [thread overview]
Message-ID: <20120619152147.9f377a64.akpm@linux-foundation.org> (raw)
In-Reply-To: <4FE0F675.3050201@hp.com>
On Tue, 19 Jun 2012 22:00:22 +0000
"Pearson, Greg" <greg.pearson@hp.com> wrote:
> I wasn't quite sure what to do about that at first either, I read
> "Documentation/SubmittingPatches" and it says:
>
> "The Signed-off-by: tag indicates that the signer was involved in the
> development of the patch, or that he/she was in the patch's delivery path."
>
> Since Yinghai contributed some code that is in the current version of
> the patch I thought the "Signed-off-by" tag would be ok, but if
> something else is more appropriate I have no problem re-cutting the
> patch to make the chain of custody more clear.
Yup, we shouldn't expect people to be able to magically infer
fine-grained details such as this from hints embedded in the signoff
trail. Fortunately we can write stuff in English ;)
I added
: This patch contains contributions from Yinghai Lu.
to the changelog. Simple, huh? :)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-06-19 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 23:47 [PATCH v4] mm/memblock: fix overlapping allocation when doubling reserved array Greg Pearson
2012-06-19 21:33 ` Tejun Heo
2012-06-19 22:00 ` Pearson, Greg
2012-06-19 22:21 ` Andrew Morton [this message]
2012-06-19 22:14 ` Andrew Morton
2012-06-19 22:35 ` Pearson, Greg
2012-06-19 23:00 ` Andrew Morton
2012-06-20 15:21 ` Pearson, Greg
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=20120619152147.9f377a64.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=greg.pearson@hp.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=shangw@linux.vnet.ibm.com \
--cc=tj@kernel.org \
--cc=yinghai@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).