mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: Shyam Saini <mayhs11saini@gmail.com>
Cc: gregkh@linuxfoundation.org, hsweeten@visionengravers.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Staging: comedi: comedi_fops.c: Fixed coding style issue
Date: Tue, 10 May 2016 17:45:14 +0100	[thread overview]
Message-ID: <5732101A.5030304@mev.co.uk> (raw)
In-Reply-To: <1462895467-10917-1-git-send-email-mayhs11saini@gmail.com>

On 10/05/16 16:51, Shyam Saini wrote:
> Fixed following checkpatch.pl warnings
> WARNING: Prefer WRITE_ONCE(<FOO>, <BAR>) over ACCESS_ONCE(<FOO>) = <BAR>
>
> WARNING: Prefer READ_ONCE(<FOO>) over ACCESS_ONCE(<FOO>)
>
> Signed-off-by: Shyam Saini <mayhs11saini@gmail.com>
> ---
>   drivers/staging/comedi/comedi_fops.c | 12 ++++++------
>   1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/comedi/comedi_fops.c b/drivers/staging/comedi/comedi_fops.c
> index 629080f..4d87596 100644
> --- a/drivers/staging/comedi/comedi_fops.c
> +++ b/drivers/staging/comedi/comedi_fops.c
> @@ -312,8 +312,8 @@ static void comedi_file_reset(struct file *file)
>   	}
>   	cfp->last_attached = dev->attached;
>   	cfp->last_detach_count = dev->detach_count;
> -	ACCESS_ONCE(cfp->read_subdev) = read_s;
> -	ACCESS_ONCE(cfp->write_subdev) = write_s;
> +	WRITE_ONCE(cfp->read_subdev, read_s);
> +	WRITE_ONCE(cfp->write_subdev, write_s);
>   }
>
>   static void comedi_file_check(struct file *file)
> @@ -331,7 +331,7 @@ static struct comedi_subdevice *comedi_file_read_subdevice(struct file *file)
>   	struct comedi_file *cfp = file->private_data;
>
>   	comedi_file_check(file);
> -	return ACCESS_ONCE(cfp->read_subdev);
> +	return READ_ONCE(cfp->read_subdev);
>   }
>
>   static struct comedi_subdevice *comedi_file_write_subdevice(struct file *file)
> @@ -339,7 +339,7 @@ static struct comedi_subdevice *comedi_file_write_subdevice(struct file *file)
>   	struct comedi_file *cfp = file->private_data;
>
>   	comedi_file_check(file);
> -	return ACCESS_ONCE(cfp->write_subdev);
> +	return READ_ONCE(cfp->write_subdev);
>   }
>
>   static int resize_async_buffer(struct comedi_device *dev,
> @@ -1992,7 +1992,7 @@ static int do_setrsubd_ioctl(struct comedi_device *dev, unsigned long arg,
>   	    !(s_old->async->cmd.flags & CMDF_WRITE))
>   		return -EBUSY;
>
> -	ACCESS_ONCE(cfp->read_subdev) = s_new;
> +	WRITE_ONCE(cfp->read_subdev, s_new);
>   	return 0;
>   }
>
> @@ -2034,7 +2034,7 @@ static int do_setwsubd_ioctl(struct comedi_device *dev, unsigned long arg,
>   	    (s_old->async->cmd.flags & CMDF_WRITE))
>   		return -EBUSY;
>
> -	ACCESS_ONCE(cfp->write_subdev) = s_new;
> +	WRITE_ONCE(cfp->write_subdev, s_new);
>   	return 0;
>   }
>
>

Thanks!

Reviewed-by: Ian Abbott <abbotti@mev.co.uk>

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk> )=-
-=(                          Web: http://www.mev.co.uk/  )=-

      reply	other threads:[~2016-05-10 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 15:51 Shyam Saini
2016-05-10 16:45 ` Ian Abbott [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=5732101A.5030304@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mayhs11saini@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

all inboxes | Powered by JetHome®