From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: "Ira W. Snyder" <iws@ovro.caltech.edu>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] liblockdep fixes for v3.14
Date: Sun, 9 Feb 2014 13:53:25 +0100 [thread overview]
Message-ID: <20140209125325.GA23318@gmail.com> (raw)
In-Reply-To: <52F2C56F.5030309@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)
>
> are available in the git repository at:
>
>
> https://github.com/sashalevin/liblockdep.git liblockdep-fixes
>
> for you to fetch changes up to a521b55af18ac72c969c1ba41b660d77dae37357:
>
> liblockdep: add a stub for new rcu_is_watching (2014-02-05 18:03:54 -0500)
>
> ----------------------------------------------------------------
> Ira W. Snyder (3):
> tools: lockdep: fix initialization code path
> tools: lockdep: fix include of asm/hash.h
> tools: lockdep: add include directory to allow tests to compile
>
> Sasha Levin (2):
> liblockdep: mark runtests.sh as executable
> liblockdep: add a stub for new rcu_is_watching
So I have a couple of nits about the commits:
1)
Please use the following standard tags/prefixes:
tools/liblockdep: Fix initialization code path
...
and also capitalize sentences properly.
2)
Faulty SOB sequences:
Author: Ira W. Snyder <iws@ovro.caltech.edu>
Date: Fri Jan 31 13:35:32 2014 -0800
tools: lockdep: add include directory to allow tests to compile
Acked-by: Sasha Levin <sasha.levin@oracle.com>
Signed-off-by: Ira W. Snyder <iws@ovro.caltech.edu>
That's not how we do signoffs, maintainer commits should be:
Signed-off-by: Ira W. Snyder <iws@ovro.caltech.edu>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
As a side note, that's not a valid Ack sequence either, which if done
should be the other way around:
Signed-off-by: Ira W. Snyder <iws@ovro.caltech.edu>
Acked-by: Sasha Levin <sasha.levin@oracle.com>
3)
It's not clear which patch you are referring to here:
This patch mirrors the fix used for perf, titled "tools: perf:
util: fix include for non x86 architectures".
It's neither in the series, nor in upstream.
Thanks,
Ingo
next prev parent reply other threads:[~2014-02-09 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 23:12 [GIT PULL] liblockdep fixes for v3.14 Sasha Levin
2014-02-09 12:53 ` Ingo Molnar [this message]
2014-02-10 1:36 ` Sasha Levin
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=20140209125325.GA23318@gmail.com \
--to=mingo@kernel.org \
--cc=iws@ovro.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--cc=tglx@linutronix.de \
/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