All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Hennerich <michael.hennerich@analog.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: naming IIO_IN_DIFF in-in
Date: Tue, 7 Jun 2011 11:00:18 +0200	[thread overview]
Message-ID: <4DEDE8A2.7030803@analog.com> (raw)

Hi Jonathan,

I wonder if naming IIO_IN_DIFF in-in is really a good idea.
Declaring the attribute in a conventional fashion doesn't work.

static IIO_DEVICE_ATTR(in-in_scale_available, S_IRUGO, \
ad7793_show_scale_available, NULL, 0);

static struct attribute *ad7793_attributes[] =3D {
&iio_dev_attr_sampling_frequency.dev_attr.attr,
&iio_const_attr_sampling_frequency_available.dev_attr.attr,
&iio_dev_attr_in-in_scale_available.dev_attr.attr,
NULL
};

drivers/staging/iio/adc/ad7793.c:681: error: expected =91=3D=92, =91,=92,=
 =91;=92,=20
=91asm=92 or =91__attribute__=92 before =91-=92 token
drivers/staging/iio/adc/ad7793.c:688: error: =91iio_dev_attr_in=92=20
undeclared here (not in a function)
drivers/staging/iio/adc/ad7793.c:688: error: =91in_scale_available=92=20
undeclared here (not in a function)

--=20
Greetings,
Michael

--
Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin,
Margaret Seif

             reply	other threads:[~2011-06-07  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  9:00 Michael Hennerich [this message]
2011-06-07  9:27 ` naming IIO_IN_DIFF in-in Jonathan Cameron
2011-06-07 11:19   ` Hennerich, Michael

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=4DEDE8A2.7030803@analog.com \
    --to=michael.hennerich@analog.com \
    --cc=jic23@cam.ac.uk \
    --cc=linux-iio@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 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.