public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Steven Miao <realmz6@gmail.com>,
	Jonathan Cameron <jic23@cam.ac.uk>,
	Michael Hennerich <michael.hennerich@analog.com>,
	adi-buildroot-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Blackfin: bf537: rename "CONFIG_AD7314"
Date: Thu, 13 Feb 2014 11:08:11 +0100	[thread overview]
Message-ID: <1392286091.30853.35.camel@x220> (raw)
In-Reply-To: <20130404120707.GA27590@roeck-us.net>

[Replaced previous maintainer and list with current maintainer and
list.]

On Thu, 2013-04-04 at 05:07 -0700, Guenter Roeck wrote:
> On Thu, Apr 04, 2013 at 12:17:03PM +0200, Paul Bolle wrote:
> > [Forwarded to a recent address of Guenter, as the ericsson address
> > bounces.]
> > 
> > Paul Bolle
> > 
> > On Thu, 2013-04-04 at 12:08 +0200, Paul Bolle wrote:
> > > In v3.2 the Analog Devices AD7314 temperature sensor driver was removed
> > > as an IIO driver and added as a HWMON driver. But it was apparently
> > > overlooked to rename two references to CONFIG_AD7314 to
> > > CONFIG_SENSORS_AD7314. Do so now. Use the IS_ENABLED() macro, while
> > > we're at it.
> > > 
> > > Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> > > ---
> > > 0) Entirely untested.
> > > 
> > > 1) See commits 4f3a659581cabf1be441d6467b523be914615496 ("hwmon: AD7314
> > > driver (ported from IIO)") and 48a2c3799b7141c271a771d3249142a104faeefc
> > > ("staging:iio:adc:ad7314 removal. Supported via hwmon.") for the two
> > > patches involved.
> > > 
> > >  arch/blackfin/mach-bf537/boards/stamp.c | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/arch/blackfin/mach-bf537/boards/stamp.c b/arch/blackfin/mach-bf537/boards/stamp.c
> > > index 23bb55d..b40b849 100644
> > > --- a/arch/blackfin/mach-bf537/boards/stamp.c
> > > +++ b/arch/blackfin/mach-bf537/boards/stamp.c
> > > @@ -681,7 +681,7 @@ static struct bfin5xx_spi_chip ad2s1210_spi_chip_info = {
> > >  };
> > >  #endif
> > >  
> > > -#if defined(CONFIG_AD7314) || defined(CONFIG_AD7314_MODULE)
> > > +#if IS_ENABLED(CONFIG_SENSORS_AD7314)
> > >  static struct bfin5xx_spi_chip ad7314_spi_chip_info = {
> > >  	.enable_dma = 0,
> > >  };
> > > @@ -1039,7 +1039,7 @@ static struct spi_board_info bfin_spi_board_info[] __initdata = {
> > >  	},
> > >  #endif
> > >  
> > > -#if defined(CONFIG_AD7314) || defined(CONFIG_AD7314_MODULE)
> > > +#if IS_ENABLED(CONFIG_SENSORS_AD7314)
> > >  	{
> > >  		.modalias = "ad7314",
> > >  		.max_speed_hz = 1000000,
> > 
> Acked-by: Guenter Roeck <linux@roeck-us.net>
> 
> Really wonder ... there should be a better solution than all those ifdefs.

This issue is still present in v3.14-rc2. Can someone please have
(another) look at this?


Paul Bolle 


      reply	other threads:[~2014-02-13 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 10:08 [PATCH] Blackfin: bf537: rename "CONFIG_AD7314" Paul Bolle
2013-04-04 10:17 ` Paul Bolle
2013-04-04 12:07   ` Guenter Roeck
2014-02-13 10:08     ` Paul Bolle [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=1392286091.30853.35.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=jic23@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=michael.hennerich@analog.com \
    --cc=realmz6@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