From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Pawel Laszczak <pawell@cadence.com>,
"linux-kernel@lists.codethink.co.uk"
<linux-kernel@lists.codethink.co.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: cdns3: include host-export,h for cdns3_host_init
Date: Fri, 18 Oct 2019 10:06:42 +0100 [thread overview]
Message-ID: <fe82dabc-c446-e132-bbfe-d79a75feece2@codethink.co.uk> (raw)
In-Reply-To: <BYAPR07MB47099123D3A6BD193491FD34DD6C0@BYAPR07MB4709.namprd07.prod.outlook.com>
On 18/10/2019 04:45, Pawel Laszczak wrote:
> Hi
>
>> The cdns3_host_init() function is declared in host-export.h
>> but host.c does not include it. Add the include to have
>> the declaration present (and remove the declaration of
>> cdns3_host_exit which is now static).
>>
>> Fixes the following sparse warning:
>>
>> drivers/usb/cdns3/host.c:58:5: warning: symbol 'cdns3_host_init' was not declared. Should it be static?
>
> It should not be static. It can be called from core.c file.
> It will be static only if CONFIG_USB_CDNS3_HOST will not be defined and in
> this case function will be declared in host-export.h as static.
I know, this isn't being made static, that's a warning.
> For me It doesn't look like driver issue.
>>
>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>> ---
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Cc: Pawel Laszczak <pawell@cadence.com>
>> Cc: Felipe Balbi <felipe.balbi@linux.intel.com>
>> Cc: "Ben Dooks
>> Cc: linux-usb@vger.kernel.org
>> ---
>> drivers/usb/cdns3/host-export.h | 1 -
>> drivers/usb/cdns3/host.c | 1 +
>> 2 files changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/usb/cdns3/host-export.h b/drivers/usb/cdns3/host-export.h
>> index b498a170b7e8..ae11810f8826 100644
>> --- a/drivers/usb/cdns3/host-export.h
>> +++ b/drivers/usb/cdns3/host-export.h
>> @@ -12,7 +12,6 @@
>> #ifdef CONFIG_USB_CDNS3_HOST
>>
>> int cdns3_host_init(struct cdns3 *cdns);
>> -void cdns3_host_exit(struct cdns3 *cdns);
>
> We can't remove this function. It is invoked from core.c file.
> If you remove it from host-export.h then it will not be visible there.
>
>>
>> #else
>>
>> diff --git a/drivers/usb/cdns3/host.c b/drivers/usb/cdns3/host.c
>> index 2733a8f71fcd..ad788bf3fe4f 100644
>> --- a/drivers/usb/cdns3/host.c
>> +++ b/drivers/usb/cdns3/host.c
>> @@ -12,6 +12,7 @@
>> #include <linux/platform_device.h>
>> #include "core.h"
>> #include "drd.h"
>> +#include "host-export.h"
>
> Why host must include this file. This function is implemented
> In host.c and is used only in core.c file .
The implementation should also have the declaration to ensure
that the implemented function matches the declared prototype in
the header
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
prev parent reply other threads:[~2019-10-18 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 12:44 [PATCH] usb: cdns3: include host-export,h for cdns3_host_init Ben Dooks (Codethink)
2019-10-18 3:45 ` Pawel Laszczak
2019-10-18 9:06 ` Ben Dooks [this message]
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=fe82dabc-c446-e132-bbfe-d79a75feece2@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.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).