From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: driverdev-devel@linuxdriverproject.org,
H Hartley Sweeten <hartleys@visionengravers.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: amplc_pci230: fix DACOUT write
Date: Mon, 8 Sep 2014 12:14:45 -0700 [thread overview]
Message-ID: <20140908191445.GA32320@kroah.com> (raw)
In-Reply-To: <1408447956-10139-1-git-send-email-abbotti@mev.co.uk>
On Tue, Aug 19, 2014 at 12:32:36PM +0100, Ian Abbott wrote:
> Commit 4f9c63fe5333b27ab23ed399830c7977f6970744 ("staging: comedi:
> amplc_pci230: refactor iobase addresses") removed some parentheses
> (presumably to keep the line withing 80 chars) in
> `pci230_ao_write_nofifo()` when writing to the DACOUT1 or DACOUT2
> registers, but it removed the wrong parentheses. Fix it.
>
> Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
> ---
> This bug is in linux-next master and staging-next.
> ---
> drivers/staging/comedi/drivers/amplc_pci230.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/comedi/drivers/amplc_pci230.c b/drivers/staging/comedi/drivers/amplc_pci230.c
> index 0fd212f..dd69e47 100644
> --- a/drivers/staging/comedi/drivers/amplc_pci230.c
> +++ b/drivers/staging/comedi/drivers/amplc_pci230.c
> @@ -628,7 +628,7 @@ static inline void pci230_ao_write_nofifo(struct comedi_device *dev,
>
> /* Write mangled datum to appropriate DACOUT register. */
> outw(pci230_ao_mangle_datum(dev, datum),
> - devpriv->daqio + ((chan) == 0) ? PCI230_DACOUT1 : PCI230_DACOUT2);
> + devpriv->daqio + (chan == 0 ? PCI230_DACOUT1 : PCI230_DACOUT2));
> }
>
> static inline void pci230_ao_write_fifo(struct comedi_device *dev,
> --
> 2.0.4
This doesn't apply to my tree anymore, is it still needed?
thanks,
greg k-h
next prev parent reply other threads:[~2014-09-08 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 11:32 [PATCH] staging: comedi: amplc_pci230: fix DACOUT write Ian Abbott
2014-09-08 19:14 ` Greg Kroah-Hartman [this message]
2014-09-08 19:34 ` Hartley Sweeten
2014-09-09 10:33 ` Ian Abbott
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=20140908191445.GA32320@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.