From: Greg KH <greg@kroah.com>
To: Randy Dunlap <randy.dunlap@oracle.com>,
Vipin Mehta <vmehta@Atheros.com>,
linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: ath6kl: Including a header file to fix a compilation error
Date: Fri, 17 Sep 2010 11:00:56 -0700 [thread overview]
Message-ID: <20100917180056.GA20199@kroah.com> (raw)
In-Reply-To: <4C93A412.2070005@oracle.com>
On Fri, Sep 17, 2010 at 10:23:30AM -0700, Randy Dunlap wrote:
> On 09/17/10 09:54, Vipin Mehta wrote:
> > The commit fixes a compilation error that was encountered while using
> > a specific kernel configuration file. The problem was the use of some
> > functions defined in <linux/semaphore.h> without including the header
> > file explicitly. It was probably working before because of the
> > dependency getting implicitly satisfied via some other header file.
> > Also, eliminating the inclusion of the same header file more than
> > once. The code needs additional cleanup and may be addressed by a
> > subsequent commit.
> >
> > Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
> > Signed-off-by: Vipin Mehta <vmehta@atheros.com>
> > ---
>
> Hi,
> Thanks for the patch, but I still get these errors & warnings:
<snip>
Ok, I'll not apply this until it is all resolved.
> > diff --git a/drivers/staging/ath6kl/miscdrv/ar3kps/ar3kpsconfig.h b/drivers/staging/ath6kl/miscdrv/ar3kps/ar3kpsconfig.h
> > index 4358834..4e5b7bf 100644
> > --- a/drivers/staging/ath6kl/miscdrv/ar3kps/ar3kpsconfig.h
> > +++ b/drivers/staging/ath6kl/miscdrv/ar3kps/ar3kpsconfig.h
> > @@ -36,15 +36,11 @@
> >
> > #include <linux/fs.h>
> > #include <linux/errno.h>
> > -#include <linux/string.h>
> > #include <linux/signal.h>
> > -#include <linux/timer.h>
> >
> >
> > #include <linux/ioctl.h>
> > -#include <linux/skbuff.h>
> > #include <linux/firmware.h>
> > -#include <linux/wait.h>
Why are you removing these?
> >
> >
> > #include <net/bluetooth/bluetooth.h>
> > diff --git a/drivers/staging/ath6kl/os/linux/cfg80211.c b/drivers/staging/ath6kl/os/linux/cfg80211.c
> > index 7a3784d..f51c5e1 100644
> > --- a/drivers/staging/ath6kl/os/linux/cfg80211.c
> > +++ b/drivers/staging/ath6kl/os/linux/cfg80211.c
> > @@ -21,8 +21,6 @@
> > // Author(s): ="Atheros"
> > //------------------------------------------------------------------------------
> >
> > -#include <linux/kernel.h>
> > -#include <linux/netdevice.h>
And this?
> > #include <linux/wireless.h>
> > #include <linux/ieee80211.h>
> > #include <net/cfg80211.h>
> > diff --git a/drivers/staging/ath6kl/os/linux/include/ar6000_drv.h b/drivers/staging/ath6kl/os/linux/include/ar6000_drv.h
> > index 8be4f55..e624883 100644
> > --- a/drivers/staging/ath6kl/os/linux/include/ar6000_drv.h
> > +++ b/drivers/staging/ath6kl/os/linux/include/ar6000_drv.h
> > @@ -24,22 +24,14 @@
> > #ifndef _AR6000_H_
> > #define _AR6000_H_
> >
> > -#include <linux/version.h>
> > -
> > -
> > -#include <generated/autoconf.h>
> > #include <linux/init.h>
> > -#include <linux/kernel.h>
> > #include <linux/sched.h>
> > #include <linux/spinlock.h>
> > -#include <linux/skbuff.h>
> > #include <linux/if_ether.h>
> > -#include <linux/netdevice.h>
> > #include <linux/etherdevice.h>
> > #include <net/iw_handler.h>
> > #include <linux/if_arp.h>
> > #include <linux/ip.h>
> > -#include <linux/semaphore.h>
> > #include <linux/wireless.h>
> > #ifdef ATH6K_CONFIG_CFG80211
> > #include <net/cfg80211.h>
And these?
All to fix the one build error?
> > diff --git a/drivers/staging/ath6kl/os/linux/include/osapi_linux.h b/drivers/staging/ath6kl/os/linux/include/osapi_linux.h
> > index ef7cc82..9892dfc 100644
> > --- a/drivers/staging/ath6kl/os/linux/include/osapi_linux.h
> > +++ b/drivers/staging/ath6kl/os/linux/include/osapi_linux.h
> > @@ -39,6 +39,7 @@
> > #include <linux/timer.h>
> > #include <linux/delay.h>
> > #include <linux/wait.h>
> > +#include <linux/semaphore.h>
Don't put #include in a .h file if at all possible please.
> >
> > #include <linux/cache.h>
> >
> > diff --git a/drivers/staging/ath6kl/os/linux/netbuf.c b/drivers/staging/ath6kl/os/linux/netbuf.c
> > index 63fa49c..15e5d04 100644
> > --- a/drivers/staging/ath6kl/os/linux/netbuf.c
> > +++ b/drivers/staging/ath6kl/os/linux/netbuf.c
> > @@ -20,8 +20,6 @@
> > //
> > // Author(s): ="Atheros"
> > //------------------------------------------------------------------------------
> > -#include <linux/kernel.h>
> > -#include <linux/skbuff.h>
Why remove these?
Totally confused,
greg k-h
next prev parent reply other threads:[~2010-09-17 18:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 16:54 [PATCH] staging: ath6kl: Including a header file to fix a compilation error Vipin Mehta
2010-09-17 17:23 ` Randy Dunlap
2010-09-17 18:00 ` Greg KH [this message]
2010-09-17 23:26 ` Vipin Mehta
2010-09-17 23:46 ` Greg KH
2010-09-18 2:06 ` Vipin Mehta
2010-09-18 5:11 ` Greg KH
2010-09-17 23:11 ` Vipin Mehta
2010-09-17 23:26 ` Greg KH
2010-09-18 2:00 ` Vipin Mehta
2010-09-18 5:12 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-09-17 0:08 Vipin Mehta
2010-09-17 0:10 ` Luis R. Rodriguez
2010-09-17 0:13 ` Vipin Mehta
2010-09-17 0:17 ` Greg KH
2010-09-17 0:14 ` Greg KH
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=20100917180056.GA20199@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-wireless@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=vmehta@Atheros.com \
/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).