From: Jonathan Cameron <jic23@cam.ac.uk>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: iio: drop "select IIO_SIMPLE_DUMMY_EVGEN"
Date: Sun, 13 Nov 2011 13:08:24 +0000 [thread overview]
Message-ID: <4EBFC148.7070409@cam.ac.uk> (raw)
In-Reply-To: <1321189545.20271.59.camel@x61.thuisdomein>
On 11/13/2011 01:05 PM, Paul Bolle wrote:
> Commit e6477000fc ("staging:iio:dummy Add event support + fake event
> generator") added "select IIO_SIMPLE_DUMMY_EVGEN if [...]". But there
> is no Kconfig symbol named IIO_SIMPLE_DUMMY_EVGEN. The select statement
> for that symbol is a nop. Drop it.
Yes, you are quite right. Looks like some dead logic from an earlier
version. My mistake.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Acked-by: Jonathan Cameron <jic23@camd.ac.uk>
> ---
> 0) Tested with "make menuconfig" before and after applying this patch.
> Identical .config files were generated, as was expected.
>
> 1) The "select IIO_DUMMY_EVGEN" of the IIO_SIMPLE_DUMMY_EVENTS Kconfig
> entry probably does what was intended here. Maybe that's why no one
> noticed.
Indeed it does.
>
> drivers/staging/iio/Kconfig | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/staging/iio/Kconfig b/drivers/staging/iio/Kconfig
> index 4ec9118..90162aa 100644
> --- a/drivers/staging/iio/Kconfig
> +++ b/drivers/staging/iio/Kconfig
> @@ -76,7 +76,6 @@ config IIO_DUMMY_EVGEN
>
> config IIO_SIMPLE_DUMMY
> tristate "An example driver with no hardware requirements"
> - select IIO_SIMPLE_DUMMY_EVGEN if IIO_SIMPLE_DUMMY_EVENTS
> help
> Driver intended mainly as documentation for how to write
> a driver. May also be useful for testing userspace code
prev parent reply other threads:[~2011-11-13 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 13:05 [PATCH] staging: iio: drop "select IIO_SIMPLE_DUMMY_EVGEN" Paul Bolle
2011-11-13 13:08 ` 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=4EBFC148.7070409@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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