From: Sasha Levin <sasha.levin@oracle.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Eunbong Song <eunb.song@samsung.com>
Subject: [GIT PULL] liblockdep fixes for 4.1
Date: Wed, 13 May 2015 16:43:37 -0400 [thread overview]
Message-ID: <5553B779.3010005@oracle.com> (raw)
Hi Ingo,
Please pull two fixes that deal with compilation errors in liblockdep.
Thanks,
Sasha
===
The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
Linux 4.1-rc1 (2015-04-26 17:59:10 -0700)
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 2480257fb17ba0fdaf62bc8c2406bd08d5e7f8f1:
tools/liblockdep: Fix compilation error (2015-05-13 06:12:20 -0400)
----------------------------------------------------------------
Eunbong Song (2):
tools/liblockdep: Fix linker error in case of cross compile
tools/liblockdep: Fix compilation error
tools/lib/lockdep/Makefile | 3 ++-
tools/lib/lockdep/uinclude/linux/kernel.h | 3 +++
2 files changed, 5 insertions(+), 1 deletion(-)
next reply other threads:[~2015-05-13 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 20:43 Sasha Levin [this message]
2015-05-15 6:45 ` [GIT PULL] liblockdep fixes for 4.1 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=5553B779.3010005@oracle.com \
--to=sasha.levin@oracle.com \
--cc=eunb.song@samsung.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