From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] liblockdep fixes for 4.4
Date: Mon, 9 Nov 2015 08:46:53 +0100 [thread overview]
Message-ID: <20151109074653.GA8625@gmail.com> (raw)
In-Reply-To: <563D15AE.9010901@oracle.com>
* Sasha Levin <sasha.levin@oracle.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Ingo,
>
> Please pull three fixes for liblockdep. Just keeping up with kernel
> code changes and new gcc versions.
>
>
> Thanks,
> Sasha
>
> ===
>
> The following changes since commit 6a13feb9c82803e2b815eca72fa7a9f5561d7861:
>
> Linux 4.3 (2015-11-01 16:05:25 -0800)
>
> 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 2b62c2dbb902625f5c5a30c0209f261b1cf15a2a:
>
> tools/liblockdep: explicitly declare lockdep API we call from liblockdep (2015-11-06 16:01:37 -0500)
>
> - ----------------------------------------------------------------
> Sasha Levin (3):
> tools/liblockdep: remove task argument from debug_check_no_locks_held
> tools/liblockdep: add userspace versions of WRITE_ONCE and RCU_INIT_POINTER
> tools/liblockdep: explicitly declare lockdep API we call from liblockdep
>
> tools/lib/lockdep/common.c | 2 +-
> tools/lib/lockdep/include/liblockdep/common.h | 2 ++
> tools/lib/lockdep/uinclude/linux/compiler.h | 2 ++
> tools/lib/lockdep/uinclude/linux/lockdep.h | 3 ++-
> 4 files changed, 7 insertions(+), 2 deletions(-)
Pulled, thanks Sasha!
Ingo
prev parent reply other threads:[~2015-11-09 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 21:03 [GIT PULL] liblockdep fixes for 4.4 Sasha Levin
2015-11-09 7:46 ` 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=20151109074653.GA8625@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.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