From: Andrew Morton <akpm@linux-foundation.org>
To: Feng Hong <hongfeng@marvell.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
"gorcunov@openvz.org" <gorcunov@openvz.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"serge.hallyn@canonical.com" <serge.hallyn@canonical.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] poweroff: fix bug in orderly_poweroff
Date: Thu, 20 Sep 2012 17:25:13 -0700 [thread overview]
Message-ID: <20120920172513.a23d061c.akpm@linux-foundation.org> (raw)
In-Reply-To: <E62404B31D39064FBDD0B843ADF05A7D2D395FCD2F@SC-VEXCH4.marvell.com>
On Thu, 20 Sep 2012 17:16:35 -0700
Feng Hong <hongfeng@marvell.com> wrote:
> I am just a graduate and it's my first time to send a patch to
> opensource, so thank you very much for reminding me the "changelog
> affairs", it seems this patch has been added to -mm tree as attached
> mail, and I have no chance to change the comments, right ? Then I must
> remember this and be careful next time. Thanks again for reminding me!
It depends. If the person who committed the patch was using a git tree
then it can be difficult for them to alter a changelog.
But the -mm tree is not mastered in git (for this and other reasons),
and I alter changelogs all the time. So please feel free to send
replacement text and I shall copy-n-paste that text straight into the patch.
next prev parent reply other threads:[~2012-09-21 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 6:37 [PATCH V2] poweroff: fix bug in orderly_poweroff hongfeng
2012-09-20 17:06 ` Serge E. Hallyn
2012-09-21 0:16 ` Feng Hong
2012-09-21 0:25 ` Andrew Morton [this message]
2012-09-21 1:45 ` Feng Hong
2012-09-21 15:30 ` Serge Hallyn
-- strict thread matches above, loose matches on Subject: below --
2012-09-19 6:32 hongfeng
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=20120920172513.a23d061c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gorcunov@openvz.org \
--cc=hongfeng@marvell.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@canonical.com \
--cc=serge@hallyn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.