From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Melike Yurtoglu <aysemelikeyurtoglu@gmail.com>,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: iio: Move export_symbol below its function
Date: Tue, 24 Feb 2015 10:21:32 +0530 [thread overview]
Message-ID: <54EC0354.8020307@linux.vnet.ibm.com> (raw)
In-Reply-To: <1424733512-22585-1-git-send-email-aysemelikeyurtoglu@gmail.com>
Hi Melike,
On 02/24/2015 04:48 AM, Melike Yurtoglu wrote:
> WARNING: "EXPORT_SYMBOL(foo); should immediately follow its
> function/variable"
> That was found by running checkpatch.
>
> Signed-off-by: Melike Yurtoglu <aysemelikeyurtoglu@gmail.com>
> ---
> drivers/staging/iio/addac/adt7316.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/addac/adt7316.c b/drivers/staging/iio/addac/adt7316.c
> index 5b11b42..18bfbf0 100644
> --- a/drivers/staging/iio/addac/adt7316.c
> +++ b/drivers/staging/iio/addac/adt7316.c
> @@ -2069,6 +2069,7 @@ static struct attribute_group adt7516_event_attribute_group = {
> };
>
> #ifdef CONFIG_PM_SLEEP
> +EXPORT_SYMBOL_GPL(adt7316_pm_ops);
> static int adt7316_disable(struct device *dev)
> {
> struct iio_dev *dev_info = dev_get_drvdata(dev);
> @@ -2086,7 +2087,6 @@ static int adt7316_enable(struct device *dev)
> }
>
> SIMPLE_DEV_PM_OPS(adt7316_pm_ops, adt7316_disable, adt7316_enable);
> -EXPORT_SYMBOL_GPL(adt7316_pm_ops);
The EXPORT_SYMBOL() is rightly under the variable definition -
adt7316_pm_ops. So why this cleanup?
Regards
Preeti U Murthy
> #endif
>
> static const struct iio_info adt7316_info = {
>
prev parent reply other threads:[~2015-02-24 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 23:18 [PATCH] Staging: iio: Move export_symbol below its function Melike Yurtoglu
2015-02-24 4:51 ` Preeti U Murthy [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=54EC0354.8020307@linux.vnet.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=aysemelikeyurtoglu@gmail.com \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.