From: Rupesh Gujare <rgujare@ozmodevices.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] staging: ozwpan: Fix compilation issue due to export.h
Date: Wed, 27 Jun 2012 10:55:19 +0100 [thread overview]
Message-ID: <4FEAD887.1080504@ozmodevices.com> (raw)
In-Reply-To: <20120626220732.GA21906@kroah.com>
On 26/06/12 23:07, Greg KH wrote:
> On Tue, Jun 26, 2012 at 01:03:40PM +0100, Rupesh Gujare wrote:
>> Fixes compilation error caused due to header file.
>>
>> Signed-off-by: Rupesh Gujare <rgujare@ozmodevices.com>
>> ---
>> drivers/staging/ozwpan/ozhcd.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/staging/ozwpan/ozhcd.c b/drivers/staging/ozwpan/ozhcd.c
>> index 251f07c..e3efa41 100644
>> --- a/drivers/staging/ozwpan/ozhcd.c
>> +++ b/drivers/staging/ozwpan/ozhcd.c
>> @@ -28,7 +28,7 @@
>> #include <linux/usb.h>
>> #include <linux/jiffies.h>
>> #include <linux/slab.h>
>> -#include <linux/export.h>
>> +#include <linux/module.h>
> I don't understand, what is this fixing? It builds for me ok here, why
> is module.h needed instead of export.h?
>
> confused,
>
Greg,
Sorry about that. Looks like I tried to compile against distribution
kernel, which was throwing error.
Please ignore this patch.
--
Regards,
Rupesh Gujare
next prev parent reply other threads:[~2012-06-27 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 12:03 [PATCH 0/3] staging: ozwpan: Update TODO & fixes Rupesh Gujare
2012-06-26 12:03 ` [PATCH 1/3] staging: ozwpan: Unregister with sysfs while unloading Rupesh Gujare
2012-06-26 12:03 ` [PATCH 2/3] staging: ozwpan: Fix compilation issue due to export.h Rupesh Gujare
2012-06-26 22:07 ` Greg KH
2012-06-27 9:55 ` Rupesh Gujare [this message]
2012-06-26 12:03 ` [PATCH 3/3] staging: ozwpan: Update TODO file Rupesh Gujare
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=4FEAD887.1080504@ozmodevices.com \
--to=rgujare@ozmodevices.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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