From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: [PATCH] rfkill: include err.h
Date: Tue, 09 Jun 2009 15:56:52 +0200 [thread overview]
Message-ID: <1244555812.4672.9.camel@johannes.local> (raw)
Since we use ERR_PTR and similar macros, we need to include linux/err.h.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
include/linux/rfkill.h | 1 +
1 file changed, 1 insertion(+)
--- wireless-testing.orig/include/linux/rfkill.h 2009-06-09 15:55:06.000000000 +0200
+++ wireless-testing/include/linux/rfkill.h 2009-06-09 15:55:20.000000000 +0200
@@ -105,6 +105,7 @@ enum rfkill_user_states {
#include <linux/mutex.h>
#include <linux/device.h>
#include <linux/leds.h>
+#include <linux/err.h>
/* this is opaque */
struct rfkill;
next reply other threads:[~2009-06-09 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 13:56 Johannes Berg [this message]
2009-06-10 0:49 ` [PATCH] rfkill: include err.h David Miller
2009-06-10 1:34 ` John W. Linville
2009-06-10 7:22 ` Johannes Berg
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=1244555812.4672.9.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sfr@canb.auug.org.au \
/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).