From: alexander.levin@verizon.com
To: "mingo@kernel.org" <mingo@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] tools/lib/lockdep: fixes for v4.15
Date: Thu, 7 Dec 2017 16:11:03 +0000 [thread overview]
Message-ID: <20171207161057.7406-1-alexander.levin@verizon.com> (raw)
The following changes since commit dabe589657ad0f9a0d6f4101e2171574f74b00bf:
Merge branch 'efi-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2017-12-06 15:20:51 -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 97897d4c145c1e8431de28dc707dc0eda2e77037:
tools/lib/lockdep: add empty declaration for early_param (2017-12-06 22:37:52 -0500)
----------------------------------------------------------------
Mengting Zhang (1):
tools/lib/lockdep: Add missing declaration of 'pr_cont()'
Sasha Levin (1):
tools/lib/lockdep: add empty declaration for early_param
tools/include/linux/kernel.h | 2 ++
tools/include/linux/lockdep.h | 1 +
2 files changed, 3 insertions(+)
Mengting Zhang (1):
tools/lib/lockdep: Add missing declaration of 'pr_cont()'
Sasha Levin (1):
tools/lib/lockdep: add empty declaration for early_param
tools/include/linux/kernel.h | 2 ++
tools/include/linux/lockdep.h | 1 +
2 files changed, 3 insertions(+)
--
2.11.0
next reply other threads:[~2017-12-07 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 16:11 alexander.levin [this message]
2017-12-07 16:11 ` [PATCH 2/2] tools/lib/lockdep: add empty declaration for early_param alexander.levin
2017-12-08 6:09 ` Ingo Molnar
2017-12-08 6:20 ` Ingo Molnar
2017-12-08 14:03 ` alexander.levin
2017-12-11 14:45 ` Ingo Molnar
2017-12-07 16:11 ` [PATCH 1/2] tools/lib/lockdep: Add missing declaration of 'pr_cont()' alexander.levin
2017-12-08 6:19 ` Ingo Molnar
2017-12-08 6:07 ` [PATCH 0/2] tools/lib/lockdep: fixes for v4.15 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=20171207161057.7406-1-alexander.levin@verizon.com \
--to=alexander.levin@verizon.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
all inboxes | Powered by JetHome®