Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: venkat.prashanth2498@gmail.com
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, knaack.h@gmx.de,
	pmeerw@pmeerw.net, linux-iio@vger.kernel.org
Subject: Re: [PATCH] gyro:adis16136: fix debugfs_simple_attr.cocci warnings
Date: Sun, 7 Jan 2018 16:37:49 +0000	[thread overview]
Message-ID: <20180107163749.6154b0c6@archlinux> (raw)
In-Reply-To: <1515315717-3950-1-git-send-email-venkat.prashanth2498@gmail.com>

On Sun,  7 Jan 2018 14:31:57 +0530
venkat.prashanth2498@gmail.com wrote:

> From: Venkat Prashanth B U <venkat.prashanth2498@gmail.com>
> 
> Use DEFINE_DEBUGFS_ATTRIBUTE rather than DEFINE_SIMPLE_ATTRIBUTE
> for debugfs files.
> 
> Semantic patch information:
> Rationale: DEFINE_SIMPLE_ATTRIBUTE + debugfs_create_file()
> imposes some significant overhead as compared to
> DEFINE_DEBUGFS_ATTRIBUTE + debugfs_create_file_unsafe().
> 
> Generated by: scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci
> 
> Signed-off-by: Venkat Prashanth B U <venkat.prashanth2498@gmail.com>
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.

Thanks,

Jonathan

> ---
>  drivers/iio/gyro/adis16136.c | 15 +++++++++------
>  1 file changed, 9 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/iio/gyro/adis16136.c b/drivers/iio/gyro/adis16136.c
> index 90ec4be..fcd4d61 100644
> --- a/drivers/iio/gyro/adis16136.c
> +++ b/drivers/iio/gyro/adis16136.c
> @@ -124,7 +124,7 @@ static int adis16136_show_product_id(void *arg, u64 *val)
> 
>  	return 0;
>  }
> -DEFINE_SIMPLE_ATTRIBUTE(adis16136_product_id_fops,
> +DEFINE_DEBUGFS_ATTRIBUTE(adis16136_product_id_fops,
>  	adis16136_show_product_id, NULL, "%llu\n");
> 
>  static int adis16136_show_flash_count(void *arg, u64 *val)
> @@ -142,18 +142,21 @@ static int adis16136_show_flash_count(void *arg, u64 *val)
> 
>  	return 0;
>  }
> -DEFINE_SIMPLE_ATTRIBUTE(adis16136_flash_count_fops,
> +DEFINE_DEBUGFS_ATTRIBUTE(adis16136_flash_count_fops,
>  	adis16136_show_flash_count, NULL, "%lld\n");
> 
>  static int adis16136_debugfs_init(struct iio_dev *indio_dev)
>  {
>  	struct adis16136 *adis16136 = iio_priv(indio_dev);
> 
> -	debugfs_create_file("serial_number", 0400, indio_dev->debugfs_dentry,
> -		adis16136, &adis16136_serial_fops);
> -	debugfs_create_file("product_id", 0400, indio_dev->debugfs_dentry,
> +	debugfs_create_file_unsafe("serial_number", 0400,
> +		indio_dev->debugfs_dentry, adis16136,
> +		&adis16136_serial_fops);
> +	debugfs_create_file_unsafe("product_id", 0400,
> +		indio_dev->debugfs_dentry,
>  		adis16136, &adis16136_product_id_fops);
> -	debugfs_create_file("flash_count", 0400, indio_dev->debugfs_dentry,
> +	debugfs_create_file_unsafe("flash_count", 0400,
> +		indio_dev->debugfs_dentry,
>  		adis16136, &adis16136_flash_count_fops);
> 
>  	return 0;
> --
> 1.9.1
> 


      reply	other threads:[~2018-01-07 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07  9:01 [PATCH] gyro:adis16136: fix debugfs_simple_attr.cocci warnings venkat.prashanth2498
2018-01-07 16:37 ` 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=20180107163749.6154b0c6@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=venkat.prashanth2498@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