From: Davidlohr Bueso <dave@gnu.org>
To: "James E.J. Bottomley" <James.Bottomley@suse.de>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] scsi-netlink: include missing types header
Date: Mon, 18 Oct 2010 13:25:36 -0300 [thread overview]
Message-ID: <1287419136.7945.4.camel@cowboy> (raw)
scsi netlink: include missing types header
This fixes this warning (found on my latest randconfig test):
scsi_netlink.h:108: found __[us]{8,16,32,64} type without #include <linux/types.h>
I know that this header is already included in linux/netlink.h so I wonder why check_header is complaining about it. If ignorable, please disregard.
Signed-off-by: Davidlohr Bueso <dave@gnu.org>
---
include/scsi/scsi_netlink.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/scsi/scsi_netlink.h b/include/scsi/scsi_netlink.h
index 58ce8fe..5cb20cc 100644
--- a/include/scsi/scsi_netlink.h
+++ b/include/scsi/scsi_netlink.h
@@ -23,7 +23,7 @@
#define SCSI_NETLINK_H
#include <linux/netlink.h>
-
+#include <linux/types.h>
/*
* This file intended to be included by both kernel and user space
--
1.7.0.4
reply other threads:[~2010-10-18 16:25 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=1287419136.7945.4.camel@cowboy \
--to=dave@gnu.org \
--cc=James.Bottomley@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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