From: Jonathan Cameron <jic23@cam.ac.uk>
To: sonic zhang <sonic.adi@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] IIO: struct iio_dev_attr should be defined as static.
Date: Tue, 06 Apr 2010 12:30:32 +0100 [thread overview]
Message-ID: <4BBB1B58.2000405@cam.ac.uk> (raw)
In-Reply-To: <1270176948.3847.1.camel@eight.analog.com>
On 04/02/10 03:55, sonic zhang wrote:
>
> Otherwise link errors "multiple definition of `iio_dev_attr_mode'"
> are reported when compile multiple different iio drivers with the
> same attribute name.
Hi Sonic,
Sorry for slow response had long weekend away from all computers!
NAK. The right place to do this is in the call of the macro, not
in the macro itself. See the many examples in hwmon....
So
static IIO_DEVICE_ATTR(accel_x, .... etc
This makes it explicit in the drivers.
There were a few calls that were missing this in the mainline driver
set but I think they are all fixed in patches that have gone to Greg
for merging. (Michael Hennerich's patch - the second one in the thread
[PATCH] IIO:sysfs.h: Use static declaration.
The first was as per your patch).
iirc there are a few exceptions where the static is in the header
due to the macro defining a pair of static structures. Not sure if
there is a cleaner way to handle that.
Thanks,
Jonathan
>
> Signed-off-by: Sonic Zhang <sonic.adi@gmail.com>
> ---
> drivers/staging/iio/sysfs.h | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/iio/sysfs.h b/drivers/staging/iio/sysfs.h
> index e501e13..39d207e 100644
> --- a/drivers/staging/iio/sysfs.h
> +++ b/drivers/staging/iio/sysfs.h
> @@ -95,16 +95,16 @@ struct iio_const_attr {
> .val2 = _val2 }
>
> #define IIO_DEVICE_ATTR(_name, _mode, _show, _store, _addr) \
> - struct iio_dev_attr iio_dev_attr_##_name \
> + static struct iio_dev_attr iio_dev_attr_##_name \
> = IIO_ATTR(_name, _mode, _show, _store, _addr)
>
>
> #define IIO_DEVICE_ATTR_2(_name, _mode, _show, _store, _addr, _val2) \
> - struct iio_dev_attr iio_dev_attr_##_name \
> + static struct iio_dev_attr iio_dev_attr_##_name \
> = IIO_ATTR_2(_name, _mode, _show, _store, _addr, _val2)
>
> #define IIO_CONST_ATTR(_name, _string) \
> - struct iio_const_attr iio_const_attr_##_name \
> + static struct iio_const_attr iio_const_attr_##_name \
> = { .string = _string, \
> .dev_attr = __ATTR(_name, S_IRUGO, iio_read_const_attr, NULL)}
>
prev parent reply other threads:[~2010-04-06 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 2:55 [PATCH] IIO: struct iio_dev_attr should be defined as static sonic zhang
2010-04-06 3:21 ` Sonic Zhang
2010-04-06 11:30 ` Jonathan Cameron [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=4BBB1B58.2000405@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sonic.adi@gmail.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