public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Sasha Levin <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: sasha.levin@oracle.com, torvalds@linux-foundation.org,
	hpa@zytor.com, peterz@infradead.org, mingo@kernel.org,
	tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: [tip:locking/urgent] tools/liblockdep: Use the rbtree header provided by common tools headers
Date: Tue, 25 Aug 2015 00:49:14 -0700	[thread overview]
Message-ID: <tip-33fef662d20a8a98bafa6b2430b845def30f616a@git.kernel.org> (raw)
In-Reply-To: <1440479985-6696-3-git-send-email-sasha.levin@oracle.com>

Commit-ID:  33fef662d20a8a98bafa6b2430b845def30f616a
Gitweb:     http://git.kernel.org/tip/33fef662d20a8a98bafa6b2430b845def30f616a
Author:     Sasha Levin <sasha.levin@oracle.com>
AuthorDate: Tue, 25 Aug 2015 01:19:45 -0400
Committer:  Ingo Molnar <mingo@kernel.org>
CommitDate: Tue, 25 Aug 2015 09:44:23 +0200

tools/liblockdep: Use the rbtree header provided by common tools headers

Recent changes to rbtree.h may break compilation. There is no
reason to use a liblockdep specific header to begin with, so
we'll use the one shared with all other tools/.

Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1440479985-6696-3-git-send-email-sasha.levin@oracle.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 tools/lib/lockdep/preload.c               | 2 +-
 tools/lib/lockdep/uinclude/linux/rbtree.h | 1 -
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/tools/lib/lockdep/preload.c b/tools/lib/lockdep/preload.c
index 0b0112c..21cdf86 100644
--- a/tools/lib/lockdep/preload.c
+++ b/tools/lib/lockdep/preload.c
@@ -5,7 +5,7 @@
 #include <stdlib.h>
 #include <sysexits.h>
 #include "include/liblockdep/mutex.h"
-#include "../../../include/linux/rbtree.h"
+#include "../../include/linux/rbtree.h"
 
 /**
  * struct lock_lookup - liblockdep's view of a single unique lock
diff --git a/tools/lib/lockdep/uinclude/linux/rbtree.h b/tools/lib/lockdep/uinclude/linux/rbtree.h
deleted file mode 100644
index 965901d..0000000
--- a/tools/lib/lockdep/uinclude/linux/rbtree.h
+++ /dev/null
@@ -1 +0,0 @@
-#include "../../../include/linux/rbtree.h"

  reply	other threads:[~2015-08-25  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  5:19 [PATCH 1/3] tools: restore export.h Sasha Levin
2015-08-25  5:19 ` [PATCH 2/3] tools/liblockdep: correct macro for WARN Sasha Levin
2015-08-25  7:48   ` [tip:locking/urgent] tools/liblockdep: Correct " tip-bot for Sasha Levin
2015-08-25  5:19 ` [PATCH 3/3] tools/liblockdep: use the rbtree header provided by common tools headers Sasha Levin
2015-08-25  7:49   ` tip-bot for Sasha Levin [this message]
2015-08-25  7:48 ` [tip:locking/urgent] tools: Restore export.h tip-bot for Sasha Levin

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=tip-33fef662d20a8a98bafa6b2430b845def30f616a@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sasha.levin@oracle.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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