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 v3.15
Date: Thu, 19 Jun 2014 13:13:43 -0400 [thread overview]
Message-ID: <53A31A47.5010904@oracle.com> (raw)
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 b2f8bdb50a426aa104f7a57ca823589869b8da6f:
tools/liblockdep: fix comparison of a boolean value with a value of 2 (2014-06-19 13:08:10 -0400)
----------------------------------------------------------------
zhangdianfang (1):
tools/liblockdep: fix comparison of a boolean value with a value of 2
tools/lib/lockdep/preload.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2014-06-19 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 17:13 Sasha Levin [this message]
2014-06-25 5:50 ` [GIT PULL] liblockdep fixes for v3.15 Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2014-05-08 18:04 Sasha Levin
2014-05-11 5:24 ` Ingo Molnar
2014-04-03 15:12 Sasha Levin
2014-04-14 11:24 ` 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=53A31A47.5010904@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox