public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Bo Liu <liubo03@inspur.com>
Cc: krzysztof.kozlowski@linaro.org, jonathanh@nvidia.com,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] memory: tegra20-emc: replace DEFINE_SIMPLE_ATTRIBUTE with DEFINE_DEBUGFS_ATTRIBUTE
Date: Tue, 1 Nov 2022 13:12:20 +0100	[thread overview]
Message-ID: <Y2ENJJ1YiSg5oHiy@orome> (raw)
In-Reply-To: <Y2EIblbX0eDgpJ35@orome>

[-- Attachment #1: Type: text/plain, Size: 2439 bytes --]

On Tue, Nov 01, 2022 at 12:52:14PM +0100, Thierry Reding wrote:
> On Tue, Nov 01, 2022 at 04:16:11AM -0400, Bo Liu wrote:
> > Fix the following coccicheck warning:
> >  drivers/memory/tegra/tegra20-emc.c:902:0-23: WARNING:
> >   tegra_emc_debug_max_rate_fops should be defined with DEFINE_DEBUGFS_ATTRIBUTE
> >  drivers/memory/tegra/tegra20-emc.c:872:0-23: WARNING:
> >   tegra_emc_debug_min_rate_fops should be defined with DEFINE_DEBUGFS_ATTRIBUTE
> > 
> > Signed-off-by: Bo Liu <liubo03@inspur.com>
> > ---
> >  drivers/memory/tegra/tegra20-emc.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> This seems incomplete: the rationale in that debugfs cocci script says
> that DEFINE_DEBUGFS_ATTRIBUTE + debugfs_create_file_unsafe() is the
> pattern to use vs. the less efficient DEFINE_SIMPLE_ATTRIBUTE +
> debugfs_create_file(). So this patch should probably use the unsafe
> function variant at the same time to take full advantage.

That said, I'm not even sure if these attributes would qualify for
debugfs_create_file_unsafe() since there's really no protection against
removal.

Overall that cocci seems a bit misleading in that it makes these changes
seem like trivial conversions. Only converting DEFINE_SIMPLE_ATTRIBUTE()
to DEFINE_DEBUGFS_ATTRIBUTE() is basically a noop, except that debugfs
has a little more overhead (for example debugfs_attr_read() wraps
simple_attr_read()), so I'm not sure if that's worth doing on its own.

Thierry

> > 
> > diff --git a/drivers/memory/tegra/tegra20-emc.c b/drivers/memory/tegra/tegra20-emc.c
> > index bd4e37b6552d..c2b4caccfae9 100644
> > --- a/drivers/memory/tegra/tegra20-emc.c
> > +++ b/drivers/memory/tegra/tegra20-emc.c
> > @@ -869,7 +869,7 @@ static int tegra_emc_debug_min_rate_set(void *data, u64 rate)
> >  	return 0;
> >  }
> >  
> > -DEFINE_SIMPLE_ATTRIBUTE(tegra_emc_debug_min_rate_fops,
> > +DEFINE_DEBUGFS_ATTRIBUTE(tegra_emc_debug_min_rate_fops,
> >  			tegra_emc_debug_min_rate_get,
> >  			tegra_emc_debug_min_rate_set, "%llu\n");
> >  
> > @@ -899,7 +899,7 @@ static int tegra_emc_debug_max_rate_set(void *data, u64 rate)
> >  	return 0;
> >  }
> >  
> > -DEFINE_SIMPLE_ATTRIBUTE(tegra_emc_debug_max_rate_fops,
> > +DEFINE_DEBUGFS_ATTRIBUTE(tegra_emc_debug_max_rate_fops,
> >  			tegra_emc_debug_max_rate_get,
> >  			tegra_emc_debug_max_rate_set, "%llu\n");
> >  
> > -- 
> > 2.27.0
> > 



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-11-01 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  8:16 [PATCH] memory: tegra20-emc: replace DEFINE_SIMPLE_ATTRIBUTE with DEFINE_DEBUGFS_ATTRIBUTE Bo Liu
2022-11-01 11:52 ` Thierry Reding
2022-11-01 12:12   ` Thierry Reding [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=Y2ENJJ1YiSg5oHiy@orome \
    --to=thierry.reding@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=liubo03@inspur.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