From: Jonathan Cameron <jic23@cam.ac.uk>
To: Hui Zhu <teawater@gmail.com>, Greg Kroah-Hartman <gregkh@suse.de>,
Michael Hennerich <michael.hennerich@analog.com>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix build error of function iio_event_getfd
Date: Sat, 26 Nov 2011 09:19:34 +0000 [thread overview]
Message-ID: <a3c3695e-8a13-4e44-9660-0df049d86003@email.android.com> (raw)
In-Reply-To: <CANFwon20C9NC6GmWnwfSHcWOSFe-7fdt_QbCQQNhegieNeDUNA@mail.gmail.com>
Thanks but this is 7th fix I have seen.
Hui Zhu <teawater@gmail.com> wrote:
>Got a build error:
> CC [M] drivers/staging/iio/industrialio-core.o
>/home/teawater/kernel2/linux/drivers/staging/iio/industrialio-core.c:
>In function ‘iio_event_getfd’:
>/home/teawater/kernel2/linux/drivers/staging/iio/industrialio-core.c:262:32:
>error: ‘ev_int’ undeclared (first use in this function)
>/home/teawater/kernel2/linux/drivers/staging/iio/industrialio-core.c:262:32:
>note: each undeclared identifier is reported only once for each
>function it appears in
>Not sure it is fixed or not.
>Post a patch for it.
>
>Signed-off-by: Hui Zhu <teawater@gmail.com>
>---
> drivers/staging/iio/industrialio-core.c | 1 +
> 1 file changed, 1 insertion(+)
>
>--- a/drivers/staging/iio/industrialio-core.c
>+++ b/drivers/staging/iio/industrialio-core.c
>@@ -243,6 +243,7 @@ static const struct file_operations iio_
> static int iio_event_getfd(struct iio_dev *indio_dev)
> {
> int fd;
>+ struct iio_event_interface *ev_int = indio_dev->event_interface;
>
> if (indio_dev->event_interface == NULL)
> return -ENODEV;
--
Sent from my Android phone
with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2011-11-26 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 8:07 Hui Zhu
2011-11-26 8:52 ` Cong Wang
2011-11-26 9:19 ` Jonathan Cameron [this message]
2011-11-27 0:54 ` Greg KH
2011-11-27 7:01 ` Hui Zhu
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=a3c3695e-8a13-4e44-9660-0df049d86003@email.android.com \
--to=jic23@cam.ac.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=teawater@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
all inboxes | Powered by JetHome®