public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishka Dasgupta <nishkadg.linux@gmail.com>
To: Ian Abbott <abbotti@mev.co.uk>,
	hsweeten@visionengravers.com, gregkh@linuxfoundation.org,
	olsonse@umich.edu, jkhasdev@gmail.com,
	giulio.benetti@micronovasrl.com, nishadkamdar@gmail.com,
	kas.sandesh@gmail.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: Remove variable runflags
Date: Fri, 31 May 2019 18:17:47 +0530	[thread overview]
Message-ID: <ceb54997-3057-81df-f3f0-e04b36e950c4@gmail.com> (raw)
In-Reply-To: <8292224d-9c4a-d29e-4a86-d3352fcd2be1@mev.co.uk>

On 31/05/19 3:55 PM, Ian Abbott wrote:
> On 30/05/2019 21:51, Nishka Dasgupta wrote:
>> Remove variable runflags and use its value directly. Issue found with
>> checkpatch.
>>
>> Signed-off-by: Nishka Dasgupta <nishkadg.linux@gmail.com>
>> ---
>>   drivers/staging/comedi/comedi_fops.c | 8 ++------
>>   1 file changed, 2 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/staging/comedi/comedi_fops.c 
>> b/drivers/staging/comedi/comedi_fops.c
>> index f6d1287c7b83..b84ee9293903 100644
>> --- a/drivers/staging/comedi/comedi_fops.c
>> +++ b/drivers/staging/comedi/comedi_fops.c
>> @@ -676,16 +676,12 @@ EXPORT_SYMBOL_GPL(comedi_is_subdevice_running);
>>   static bool __comedi_is_subdevice_running(struct comedi_subdevice *s)
>>   {
>> -    unsigned int runflags = __comedi_get_subdevice_runflags(s);
>> -
>> -    return comedi_is_runflags_running(runflags);
>> +    return 
>> comedi_is_runflags_running(__comedi_get_subdevice_runflags(s));
>>   }
>>   bool comedi_can_auto_free_spriv(struct comedi_subdevice *s)
>>   {
>> -    unsigned int runflags = __comedi_get_subdevice_runflags(s);
>> -
>> -    return runflags & COMEDI_SRF_FREE_SPRIV;
>> +    return __comedi_get_subdevice_runflags(s) & COMEDI_SRF_FREE_SPRIV;
>>   }
>>   /**
>>
> 
> I couldn't reproduce this checkpatch issue, even with '--subjective'.

I'm sorry, that was extremely careless of me. I used Coccinelle to find 
this, not Checkpatch.
Here is the Coccinelle script I used:

@@identifier i1, i2, f1, f2; type T; expression e1, e2; statement S1, S2;@@
(
- T i1 = f1(...);
|
- T i1 = e1;
)
... when != e2 = <+...i1...+>
     when != if (<+...i1...+>) S1 else S2
     when != f2(...,<+...i1...+>,...)
     when != i1->i2
     when != i2[<+...i1...+>]
     when != while(<+...i1...+>) S1
     when != for(...;<+...i1...+>;...) S1

Again, I'm sorry for the confusion; I don't know why it happened, but it 
won't happen again.

Nishka


  reply	other threads:[~2019-05-31 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 20:51 [PATCH] staging: comedi: Remove variable runflags Nishka Dasgupta
2019-05-31 10:25 ` Ian Abbott
2019-05-31 12:47   ` Nishka Dasgupta [this message]
2019-05-31 13:31     ` Dan Carpenter

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=ceb54997-3057-81df-f3f0-e04b36e950c4@gmail.com \
    --to=nishkadg.linux@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=giulio.benetti@micronovasrl.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=jkhasdev@gmail.com \
    --cc=kas.sandesh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nishadkamdar@gmail.com \
    --cc=olsonse@umich.edu \
    /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