From: Ian Abbott <abbotti@mev.co.uk>
To: "Spencer E. Olson" <olsonse@umich.edu>, devel@driverdev.osuosl.org
Cc: H Hartley Sweeten <hsweeten@visionengravers.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] staging: comedi: ni_tiocmd: change mistaken use of start_src for start_arg
Date: Tue, 12 Jan 2016 17:56:02 +0000 [thread overview]
Message-ID: <56953E32.10101@mev.co.uk> (raw)
In-Reply-To: <1452619998-14586-1-git-send-email-olsonse@umich.edu>
On 12/01/16 17:33, Spencer E. Olson wrote:
> This fixes a bug in function ni_tio_input_inttrig(). The trigger number
> should be compared to cmd->start_arg, not cmd->start_src.
>
> Fixes: 6a760394d7eb ("staging: comedi: ni_tiocmd: clarify the
> cmd->start_arg validation and use")
> Cc: <stable@vger.kernel.org> # 3.17+
> Signed-off-by: Spencer E. Olson <olsonse@umich.edu>
> ---
> Added description suggested by Ian and Dan. Added Fixes:, CC: tags as
> suggested by Ian.
>
> drivers/staging/comedi/drivers/ni_tiocmd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
It's okay, except that I don't think you can split the Fixes: line like
that. (Maybe you can split it by prefixing the continuation lines with
whitespace, but it's easier to grep if it's all on one line, and this is
a valid exemption to checkpatch warnings about line lengths in the
description.)
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2016-01-12 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56951A9A.8060409@mev.co.uk>
2016-01-12 17:33 ` [PATCH v2] staging: comedi: ni_tiocmd: change mistaken use of start_src for start_arg Spencer E. Olson
2016-01-12 17:56 ` Ian Abbott [this message]
[not found] ` <CAOx9PeiUWp6DPw+PFKDyZXc1s3kF9pGfhW1oc+JSZ3nGf-5_Mw@mail.gmail.com>
2016-01-13 10:36 ` Ian Abbott
2016-01-13 10:56 ` Dan Carpenter
2016-01-12 22:12 ` Dan Carpenter
2016-01-13 10:37 ` 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=56953E32.10101@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=olsonse@umich.edu \
--cc=stable@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.