From: tip-bot for Elena Reshetova <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, torvalds@linux-foundation.org, hpa@zytor.com,
peterz@infradead.org, elena.reshetova@intel.com,
tglx@linutronix.de, acme@redhat.com,
linux-kernel@vger.kernel.org
Subject: [tip:locking/urgent] locking/refcounts: Add missing kernel.h header to have UINT_MAX defined
Date: Fri, 24 Feb 2017 01:17:59 -0800 [thread overview]
Message-ID: <tip-318b1dedcd39012624f466d281627553e9fa2570@git.kernel.org> (raw)
In-Reply-To: <1487855374-21993-1-git-send-email-elena.reshetova@intel.com>
Commit-ID: 318b1dedcd39012624f466d281627553e9fa2570
Gitweb: http://git.kernel.org/tip/318b1dedcd39012624f466d281627553e9fa2570
Author: Elena Reshetova <elena.reshetova@intel.com>
AuthorDate: Thu, 23 Feb 2017 15:09:34 +0200
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 24 Feb 2017 09:02:10 +0100
locking/refcounts: Add missing kernel.h header to have UINT_MAX defined
Fix header dependency.
Suggested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: Elena Reshetova <elena.reshetova@intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
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/1487855374-21993-1-git-send-email-elena.reshetova@intel.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
include/linux/refcount.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/refcount.h b/include/linux/refcount.h
index 0e8cfb2..0023fee 100644
--- a/include/linux/refcount.h
+++ b/include/linux/refcount.h
@@ -4,6 +4,7 @@
#include <linux/atomic.h>
#include <linux/mutex.h>
#include <linux/spinlock.h>
+#include <linux/kernel.h>
typedef struct refcount_struct {
atomic_t refs;
parent reply other threads:[~2017-02-24 9:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1487855374-21993-1-git-send-email-elena.reshetova@intel.com>]
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-318b1dedcd39012624f466d281627553e9fa2570@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=elena.reshetova@intel.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=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
Powered by JetHome