From: Sasha Levin <sasha.levin@oracle.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] liblockdep fixes for 4.4
Date: Fri, 6 Nov 2015 16:03:42 -0500 [thread overview]
Message-ID: <563D15AE.9010901@oracle.com> (raw)
-----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(-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJWPRWnAAoJEN6mb/eXdyzcWLMP/iJshjLbujVUmZjhuwz2bC3D
BSQfr0ZlT7FyLpCpEEE4F9Wk46L5cSC3+RDGT/kAKamhD/cLL/X/JLSIFBOFIll2
Ka+Ipq/VG3qAqssus2S+JkCWJZJlKpfdp7DzBQUxU+TyarSG5Yc5FOPbIcqyFOBn
ZCTYziu/SNQ/Bmv0y+SYP2tcPRIF7VoXbgXKXHXiD10r6xHJHF7kFsHqPpfl9F2A
wOqHfl8j6ZxDvSvgdvXFK9ywHWsS2AJgk8Ebj0R6QRs37bR9LBONlBDD1g+m1hlY
WCquwndww/zZjGkb+PD/hD7ceJ/wiDslLkMsBHIYfPCuoqm/iJiOeZIqyhDFaijX
nnu0x76i21TccMN09h2oFHaBGAIsCwYkXcQSi5YZxSHAf+BwzVUK8wpfOPYljnc7
X2/Lh0qp+JdjqWzB4LR7um1BPtWVgdFxU5fTTT7idH0kBXs8uVFsL3L4WMeiL/H/
nraaeegIG/T8T7qvBhmfSv7pXrCxyd8qThe4gTcg5/89BbZl0fjq6ulg5l/Clei1
bJcOczut0aP0Qfc/bjQrXYpI7z5U/pmHMA1dlMsKXZTwpsB1vuj2QjbYjVg8VHLx
GRIeyDFkq/G21DQ3khPPE8zdOG4E3p0g9Js9phplbelnQb0UsmiRffpM16HboufS
STRBksKAITetI6aolOKB
=Ddfc
-----END PGP SIGNATURE-----
next reply other threads:[~2015-11-06 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 21:03 Sasha Levin [this message]
2015-11-09 7:46 ` [GIT PULL] liblockdep fixes for 4.4 Ingo Molnar
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=563D15AE.9010901@oracle.com \
--to=sasha.levin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/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.