From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org >> LKML"
<linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL v2] liblockdep fixes for v3.14
Date: Sat, 22 Feb 2014 18:33:11 +0100 [thread overview]
Message-ID: <20140222173311.GA401@gmail.com> (raw)
In-Reply-To: <52FBFEE8.3010708@oracle.com>
* Sasha Levin <sasha.levin@oracle.com> wrote:
> The following changes since commit 65370bdf881e20907e7a53abab9b8c0bc5f60a6b:
>
> Merge branch 'linus' into core/locking (2014-02-02 09:43:20 +0100)
That's not a suitable base commit for upstream fixes (because it
brings in tip:core/locking changes destined for v3.15!) - please use
tip:core/urgent or one of Linus's -rc's.
Also, I found some more commit log problems.
1)
This:
Acked-by: Sasha Levin <sasha.levin@oracle.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Is redundant - skip the Acked-by.
2)
This:
[sasha: Modified subject]
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
should in general be:
[ Modified subject. ]
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Because it's obvious from the placement of the bracketed line that the
comment is from you, no need to prefix it with 'sasha:'.
But ... more importantly, small commit log edits are typical (and
expected) from maintainers - I do it for 99% of the patches that I
apply, so please only add such comments if it goes outside the usual
pattern:
- if you've written a completely new changelog (nice from you)
- or if you've resolved conflicts when applying the patch or
actually changed the code logic compared to what was submitted
(which should always be declared).
Thanks,
Ingo
prev parent reply other threads:[~2014-02-22 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 23:08 [GIT PULL v2] liblockdep fixes for v3.14 Sasha Levin
2014-02-22 17:33 ` Ingo Molnar [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=20140222173311.GA401@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sasha.levin@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