From: Greg KH <gregkh@suse.de>
To: Stephane Pajot <pajot.stephane@gmail.com>
Cc: arun.thomas@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Staging: comedi: fix tabulation and over 80 chars issues in amplc_pci224.c This is a patch to the amplc_pci224.c file that fixes up tabulation style errors and over 80 chars warning found by the checkpatch.pl tool Signed-off-by: Stephane Pajot <pajot.stephane@gmail.com>
Date: Thu, 12 May 2011 10:23:45 -0700 [thread overview]
Message-ID: <20110512172345.GC14812@suse.de> (raw)
In-Reply-To: <1305218698-7889-1-git-send-email-pajot.stephane@gmail.com>
On Thu, May 12, 2011 at 06:44:58PM +0200, Stephane Pajot wrote:
> ---
> drivers/staging/comedi/drivers/amplc_pci224.c | 63 +++++++++++++------------
> 1 files changed, 33 insertions(+), 30 deletions(-)
>
> diff --git a/drivers/staging/comedi/drivers/amplc_pci224.c b/drivers/staging/comedi/drivers/amplc_pci224.c
> index 1b5ba1c..2f61358 100644
> --- a/drivers/staging/comedi/drivers/amplc_pci224.c
> +++ b/drivers/staging/comedi/drivers/amplc_pci224.c
> @@ -52,33 +52,33 @@ Supports:
> Configuration options - PCI224:
> [0] - PCI bus of device (optional).
> [1] - PCI slot of device (optional).
> - If bus/slot is not specified, the first available PCI device
> - will be used.
> + If bus/slot is not specified, the first available PCI device
> + will be used.
Why did you change these comment lines?
> @@ -401,7 +401,8 @@ MODULE_DEVICE_TABLE(pci, pci224_pci_table);
>
> /* this structure is for data unique to this hardware driver. If
> several hardware drivers keep similar information in this structure,
> - feel free to suggest moving the variable to the struct comedi_device struct. */
> + feel free to suggest moving the variable
> + to the struct comedi_device struct. */
If you are going to change a multi-line comment like this, please use
the proper formatting for it. Your change didn't really help anything
here.
> struct pci224_private {
> struct pci_dev *pci_dev; /* PCI device */
> const unsigned short *hwrange;
> @@ -678,12 +679,14 @@ static void pci224_ao_handle_fifo(struct comedi_device *dev,
> switch (dacstat & PCI224_DACCON_FIFOFL_MASK) {
> case PCI224_DACCON_FIFOFL_EMPTY:
> room = PCI224_FIFO_ROOM_EMPTY;
> - if (!devpriv->ao_stop_continuous && devpriv->ao_stop_count == 0) {
> - /* FIFO empty at end of counted acquisition. */
> - pci224_ao_stop(dev, s);
> - s->async->events |= COMEDI_CB_EOA;
> - comedi_event(dev, s);
> - return;
> + if (!devpriv->ao_stop_continuous == 0) {
> + if (devpriv->ao_stop_count == 0) {
You just changed the logic of this if statment, not good at all.
thanks,
greg k-h
prev parent reply other threads:[~2011-05-12 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 16:44 [PATCH 2/2] Staging: comedi: fix tabulation and over 80 chars issues in amplc_pci224.c This is a patch to the amplc_pci224.c file that fixes up tabulation style errors and over 80 chars warning found by the checkpatch.pl tool Signed-off-by: Stephane Pajot <pajot.stephane@gmail.com> Stephane Pajot
2011-05-12 17:23 ` Greg KH [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=20110512172345.GC14812@suse.de \
--to=gregkh@suse.de \
--cc=arun.thomas@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pajot.stephane@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