From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: "S. Lockwood-Childs" <sjl@dent.vctlabs.com>,
zhangdianfang <zhangdianfang@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL v2] liblockdep fixes for v3.15
Date: Wed, 16 Jul 2014 13:53:45 +0200 [thread overview]
Message-ID: <20140716115345.GD28434@gmail.com> (raw)
In-Reply-To: <53BACA23.9010907@oracle.com>
* Sasha Levin <sasha.levin@oracle.com> wrote:
> The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
>
> Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git liblockdep-fixes
>
> for you to fetch changes up to b10827814e9c81c5a14fb73c5a6e06bd85df3f94:
>
> tools/liblockdep: Account for bitfield changes in lockdeps lock_acquire (2014-07-07 12:20:16 -0400)
>
> ----------------------------------------------------------------
> S. Lockwood-Childs (1):
> tools/liblockdep: Account for bitfield changes in lockdeps lock_acquire
>
> Sasha Levin (1):
> tools/liblockdep: Remove debug print left over from development
>
> zhangdianfang (1):
> tools/liblockdep: Fix comparison of a boolean value with a value of 2
>
> tools/lib/lockdep/include/liblockdep/mutex.h | 4 ++--
> tools/lib/lockdep/include/liblockdep/rwlock.h | 8 ++++----
> tools/lib/lockdep/preload.c | 20 +++++++++-----------
> 3 files changed, 15 insertions(+), 17 deletions(-)
Pulled, thanks Sasha!
Ingo
prev parent reply other threads:[~2014-07-16 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 16:26 [GIT PULL v2] liblockdep fixes for v3.15 Sasha Levin
2014-07-16 11:53 ` 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=20140716115345.GD28434@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=sjl@dent.vctlabs.com \
--cc=tglx@linutronix.de \
--cc=zhangdianfang@huawei.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.