From: Ian Abbott <abbotti@mev.co.uk>
To: devel@driverdev.osuosl.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ian Abbott <abbotti@mev.co.uk>,
linux-kernel@vger.kernel.org, Spencer Olson <olsonse@umich.edu>
Subject: [PATCH 0/2] staging: comedi: ni_routes: fix some regressions
Date: Tue, 14 Jan 2020 18:25:30 +0000 [thread overview]
Message-ID: <20200114182532.132058-1-abbotti@mev.co.uk> (raw)
Fix some regressions resulting from the routing functionality
implemented for the National Instruments comedi drivers in kernel 4.20
when board-specific routing information is absent.
Patch 1 fixes a null pointer dereference, but the set-up of asynchronous
commands that use external triggers on boards with missing
board-specific routing information will now fail gracefully with an
error.
Patch 2 allows routing values for the device family to be filled in even
if the board-specific routing information is missing, which should allow
asynchronous commands that use external triggers to be used on these
boards.
1) staging: comedi: ni_routes: fix null dereference in ni_find_route_source()
2) staging: comedi: ni_routes: allow partial routing information
drivers/staging/comedi/drivers/ni_routes.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
Cc: Spencer Olson <olsonse@umich.edu>
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2020-01-14 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 18:25 Ian Abbott [this message]
2020-01-14 18:25 ` [PATCH 1/2] staging: comedi: ni_routes: fix null dereference in ni_find_route_source() Ian Abbott
2020-01-14 18:25 ` [PATCH 2/2] staging: comedi: ni_routes: allow partial routing information 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=20200114182532.132058-1-abbotti@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).