All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: julia.lawall@lip6.fr, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: sw_device: make the function argument as const
Date: Sat, 14 Oct 2017 19:21:16 +0100	[thread overview]
Message-ID: <20171014192116.73c29a26@archlinux> (raw)
In-Reply-To: <1507730747-13462-1-git-send-email-bhumirks@gmail.com>

On Wed, 11 Oct 2017 16:05:47 +0200
Bhumika Goyal <bhumirks@gmail.com> wrote:

> This is a follow-up patch for:
> https://patchwork.kernel.org/patch/9999649/
> 
> Make the argument of the function iio_swd_group_init_type_name const as
> it is only passed to the function config_group_init_type_name having the
> argument as const.
> 
> Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>

As mentioned before, please put together a single series with the
dependencies and the patches making use of them.

Otherwise, this is going to take a long time to merge.

Jonathan

> ---
> This change allows a lot of config_item_type structures to be const.
> 
>  include/linux/iio/sw_device.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/iio/sw_device.h b/include/linux/iio/sw_device.h
> index fa79319..8642b91 100644
> --- a/include/linux/iio/sw_device.h
> +++ b/include/linux/iio/sw_device.h
> @@ -60,7 +60,7 @@ struct iio_sw_device *to_iio_sw_device(struct config_item *item)
>  static inline
>  void iio_swd_group_init_type_name(struct iio_sw_device *d,
>  				  const char *name,
> -				  struct config_item_type *type)
> +				  const struct config_item_type *type)
>  {
>  #if IS_ENABLED(CONFIG_CONFIGFS_FS)
>  	config_group_init_type_name(&d->group, name, type);


      reply	other threads:[~2017-10-14 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 14:05 [PATCH] iio: sw_device: make the function argument as const Bhumika Goyal
2017-10-14 18:21 ` 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=20171014192116.73c29a26@archlinux \
    --to=jic23@kernel.org \
    --cc=bhumirks@gmail.com \
    --cc=julia.lawall@lip6.fr \
    --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 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.