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, 03 Apr 2014 11:12:13 -0400 [thread overview]
Message-ID: <533D7A4D.3090900@oracle.com> (raw)
Hi Ingo,
There are two patches from liblockdep this time around:
1. There was a build breakage caused by marking a function 'asmlinkage'
in lockdep.h. Fix that by ignoring asmlinkage and visible annotations.
2. Josh Boyer mentioned that Fedora would like to include liblockdep
as a package, so we had to fix our versioning methods from being dumb
and pointless to something actually usable. So now liblockdep.so tracks
the kernel version which makes lives of distro folks much easier.
==
The following changes since commit 01d5f3b598b18a5035426c30801adf65822dbd0c:
Merge branch 'for-3.15' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata (2014-03-31 15:27:37 -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 be227b45fb228adff4371b8de9e3989904209ff4:
tools/liblockdep: Add proper versioning to the shared obj (2014-04-01 11:46:10 -0400)
----------------------------------------------------------------
Sasha Levin (2):
tools/liblockdep: Ignore asmlinkage and visible
tools/liblockdep: Add proper versioning to the shared obj
tools/lib/lockdep/Makefile | 15 ++++-----------
tools/lib/lockdep/uinclude/linux/lockdep.h | 3 +++
2 files changed, 7 insertions(+), 11 deletions(-)
next reply other threads:[~2014-04-03 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 15:12 Sasha Levin [this message]
2014-04-14 11:24 ` [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-06-19 17:13 Sasha Levin
2014-06-25 5:50 ` 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=533D7A4D.3090900@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.