All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Vianney le Clément de Saint-Marcq"
	<vianney.leclement@essensium.com>,
	linux-iio@vger.kernel.org
Cc: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Subject: Re: [PATCH] iio: mlx90614: Fix duplicate const warning
Date: Sat, 18 Apr 2015 17:30:32 +0100	[thread overview]
Message-ID: <553286A8.1010507@kernel.org> (raw)
In-Reply-To: <1429279535-19730-1-git-send-email-vianney.leclement@essensium.com>

On 17/04/15 15:05, Vianney le Clément de Saint-Marcq wrote:
> Fix a typo triggering a duplicate const warning on some compilers.
> 
> Signed-off-by: Vianney le Clément de Saint-Marcq <vianney.leclement@essensium.com>
> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play.  I'm not bothering to push this
out faster as it is afterall just a warning and has no actually effect.
> ---
>  drivers/iio/temperature/mlx90614.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/temperature/mlx90614.c b/drivers/iio/temperature/mlx90614.c
> index 06b7b96..b2d3b56 100644
> --- a/drivers/iio/temperature/mlx90614.c
> +++ b/drivers/iio/temperature/mlx90614.c
> @@ -263,7 +263,7 @@ static int mlx90614_write_raw(struct iio_dev *indio_dev,
>  }
>  
>  static int mlx90614_write_raw_get_fmt(struct iio_dev *indio_dev,
> -				     const struct iio_chan_spec const *channel,
> +				     struct iio_chan_spec const *channel,
>  				     long mask)
>  {
>  	switch (mask) {
> 


      reply	other threads:[~2015-04-18 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 14:05 [PATCH] iio: mlx90614: Fix duplicate const warning Vianney le Clément de Saint-Marcq
2015-04-18 16:30 ` 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=553286A8.1010507@kernel.org \
    --to=jic23@kernel.org \
    --cc=arnout@mind.be \
    --cc=linux-iio@vger.kernel.org \
    --cc=vianney.leclement@essensium.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 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.