linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Levin, Alexander" <alexander.levin@verizon.com>
To: "mingo@redhat.com" <mingo@redhat.com>,
	"peterz@infradead.org" <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Levin, Alexander" <alexander.levin@verizon.com>
Subject: [PATCH resend 0/8] liblockdep fixes for 3.8
Date: Fri, 29 Jul 2016 23:02:12 -0400	[thread overview]
Message-ID: <1469847222-21313-1-git-send-email-alexander.levin@verizon.com> (raw)

Hi Ingo,

A bunch of fixes that I dropped the ball on back in 3.7.

Mostly compilation fixes for errors that have happened
due to changes on the kernel side in 3.7.

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(-)

-- 
2.7.4

             reply	other threads:[~2016-07-30  3:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-30  3:02 Levin, Alexander [this message]
2016-07-30  3:02 ` [PATCH 1/8] liblockdep: Fix undefined symbol prandom_u32 Levin, Alexander
2016-07-30  3:02 ` [PATCH 4/8] liblockdep: Enable -Wall by default Levin, Alexander
2016-07-30  3:02 ` [PATCH 2/8] liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing lock_chain::depth Levin, Alexander
2016-07-30  3:02 ` [PATCH 3/8] liblockdep: Define the ARRAY_SIZE() macro Levin, Alexander
2016-07-30  3:02 ` [PATCH 6/8] liblockdep: Fix 'set but not used' warnings Levin, Alexander
2016-07-30  3:02 ` [PATCH 5/8] liblockdep: Fix 'unused value' warnings Levin, Alexander
2016-07-30  3:02 ` [PATCH 7/8] liblockdep: Fix 'defined but not used' warning for init_utsname() Levin, Alexander
2016-07-30  3:02 ` [PATCH 8/8] liblockdep: Remove -lpthread compiler option Levin, Alexander
  -- strict thread matches above, loose matches on Subject: below --
2016-07-30  2:59 [PATCH resend 0/8] liblockdep fixes for 3.8 Levin, Alexander

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=1469847222-21313-1-git-send-email-alexander.levin@verizon.com \
    --to=alexander.levin@verizon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).