public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: [GIT PULL] liblockdep fixes for 4.7
Date: Fri, 17 Jun 2016 23:17:09 -0400	[thread overview]
Message-ID: <5764BD35.4050202@oracle.com> (raw)

Hey Ingo,

Please pull a bunch of fixes for liblockdep from Ben and Vishal.

Mostly build failures as a result of kernel changes.


Thanks,
Sasha

===

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git HEAD

for you to fetch changes up to d7906160b2bc8f1be513b7e01b8783a50637092c:

  liblockdep: Remove -lpthread compiler option (2016-06-14 18:13:49 -0400)

----------------------------------------------------------------
Ben Hutchings (7):
      liblockdep: Fix undefined symbol prandom_u32
      liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing lock_chain::depth
      liblockdep: Define the ARRAY_SIZE() macro
      liblockdep: Enable -Wall by default
      liblockdep: Fix 'unused value' warnings
      liblockdep: Fix 'set but not used' warnings
      liblockdep: Fix 'defined but not used' warning for init_utsname()

Vishal Thanki (1):
      liblockdep: Remove -lpthread compiler option

 tools/lib/lockdep/Makefile                     |  1 +
 tools/lib/lockdep/lockdep.c                    | 17 +++++++++++++++++
 tools/lib/lockdep/run_tests.sh                 |  4 ++--
 tools/lib/lockdep/uinclude/linux/debug_locks.h |  2 +-
 tools/lib/lockdep/uinclude/linux/irqflags.h    |  8 ++++----
 tools/lib/lockdep/uinclude/linux/kernel.h      | 14 +++++++++++---
 tools/lib/lockdep/uinclude/linux/lockdep.h     | 18 ++++++------------
 7 files changed, 42 insertions(+), 22 deletions(-)

                 reply	other threads:[~2016-06-18  3:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5764BD35.4050202@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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