From: Jonathan Cameron <jic23@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Daniel Baluta <daniel.baluta@intel.com>,
Cristina Opriceana <cristina.opriceana@gmail.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RESEND] staging: iio: select IRQ_WORK for IIO_DUMMY_EVGEN
Date: Sat, 5 Dec 2015 17:36:07 +0000 [thread overview]
Message-ID: <56632087.20104@kernel.org> (raw)
In-Reply-To: <1589979.s93Dkm5ubV@wuerfel>
On 03/12/15 23:28, Arnd Bergmann wrote:
> The iio dummy code was recently changed to use irq_work_queue, but
> that code is compiled into the kernel only if IRQ_WORK is set, so
> we can get a link error here:
>
> drivers/built-in.o: In function `iio_evgen_poke':
> (.text+0x208a04): undefined reference to `irq_work_queue'
>
> This changes the Kconfig file to match what other drivers do.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: fd2bb310ca3d ("Staging: iio: Move evgen interrupt generation to irq_work")
> Acked-by: Daniel Baluta <daniel.baluta@intel.com>
> ---
> I submitted the patch before and it was accepted, but then it
> apparently got lost when the driver was moved out of staging,
> and the bug came back with today's linux-next
Good spot - thanks Arnd - this probably explains an odd merge conflict
that turned up around that Kconfig. Completely missed this sorry about that!
Have applied to my togreg branch - but there is a slightly delay on this going
to Greg from another issue that needs to get sorted so might be a few days
before the fix reaches next.
Pushed out as testing for the autobuilders to play with it.
Thanks,
Jonathan
>
>
> diff --git a/drivers/iio/dummy/Kconfig b/drivers/iio/dummy/Kconfig
> index e8676aa97d62..71805ced1aae 100644
> --- a/drivers/iio/dummy/Kconfig
> +++ b/drivers/iio/dummy/Kconfig
> @@ -5,7 +5,8 @@ menu "IIO dummy driver"
> depends on IIO
>
> config IIO_DUMMY_EVGEN
> - tristate
> + select IRQ_WORK
> + tristate
>
> config IIO_SIMPLE_DUMMY
> tristate "An example driver with no hardware requirements"
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-12-05 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 23:28 [PATCH, RESEND] staging: iio: select IRQ_WORK for IIO_DUMMY_EVGEN Arnd Bergmann
2015-12-05 17:36 ` 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=56632087.20104@kernel.org \
--to=jic23@kernel.org \
--cc=arnd@arndb.de \
--cc=cristina.opriceana@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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