From: "John W. Linville" <linville@tuxdriver.com>
To: jeff@garzik.org
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Holger Schurig <hs4233@mail.mn-solutions.de>,
"John W. Linville" <linville@tuxdriver.com>
Subject: [PATCH] zd1211rw: fix a double include
Date: Thu, 18 Oct 2007 21:51:25 -0400 [thread overview]
Message-ID: <11927586853636-git-send-email-linville@tuxdriver.com> (raw)
In-Reply-To: <20071018220946.GH8510@tuxdriver.com>
From: Holger Schurig <hs4233@mail.mn-solutions.de>
This patch removes all double includes of the same file. This
makes scripts/checkincludes.pl happy.
Signed-off-by: Holger Schurig <hs4233@mail.mn-solutions.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
Jeff, I missed the zd1211rw hunk of the "double includes" patch. Could
you apply this one manually?
Thanks,
John
drivers/net/wireless/zd1211rw/zd_def.h | 1 -
2 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/zd1211rw/zd_def.h b/drivers/net/wireless/zd1211rw/zd_def.h
index deb99d1..505b4d7 100644
--- a/drivers/net/wireless/zd1211rw/zd_def.h
+++ b/drivers/net/wireless/zd1211rw/zd_def.h
@@ -21,7 +21,6 @@
#include <linux/kernel.h>
#include <linux/stringify.h>
#include <linux/device.h>
-#include <linux/kernel.h>
typedef u16 __nocast zd_addr_t;
--
1.5.2.4
next prev parent reply other threads:[~2007-10-19 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 22:09 Please pull 'fixes-jgarzik' branch of wireless-2.6 John W. Linville
2007-10-19 1:51 ` John W. Linville [this message]
2007-10-20 3:06 ` [PATCH] zd1211rw: fix a double include Jeff Garzik
[not found] ` <20071018220946.GH8510-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-10-20 3:04 ` Please pull 'fixes-jgarzik' branch of wireless-2.6 Jeff Garzik
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=11927586853636-git-send-email-linville@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).