From: Oscar Carter <oscar.carter@gmx.com>
To: Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Oscar Carter <oscar.carter@gmx.com>,
Quentin Deslandes <quentin.deslandes@itdev.co.uk>,
Malcolm Priestley <tvboxspy@gmail.com>,
Amir Mahdi Ghorbanian <indigoomega021@gmail.com>,
Stefano Brivio <sbrivio@redhat.com>,
"John B. Wyatt IV" <jbwyatt4@gmail.com>,
Colin Ian King <colin.king@canonical.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] staging: vt6656: Check the return value of vnt_control_out_* calls
Date: Sat, 18 Apr 2020 14:36:57 +0200 [thread overview]
Message-ID: <20200418123659.4475-1-oscar.carter@gmx.com> (raw)
This patch series checks the return value of vnt_control_out_* function
calls.
The first patch checks the return value and when necessary modify the
function prototype to be able to return the new checked error code.
The second patch replaces the documentation of functions that their
prototype has changed by the kernel-doc style, fixing the parameters and
return value.
Oscar Carter (2):
staging: vt6656: Check the return value of vnt_control_out_* calls
staging: vt6656: Fix functions' documentation
drivers/staging/vt6656/baseband.c | 35 +++---
drivers/staging/vt6656/baseband.h | 4 +-
drivers/staging/vt6656/card.c | 198 +++++++++++++++---------------
drivers/staging/vt6656/card.h | 18 +--
drivers/staging/vt6656/mac.c | 143 ++++++++++-----------
drivers/staging/vt6656/mac.h | 26 ++--
drivers/staging/vt6656/power.c | 24 ++--
drivers/staging/vt6656/power.h | 2 +-
8 files changed, 217 insertions(+), 233 deletions(-)
--
2.20.1
next reply other threads:[~2020-04-18 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 12:36 Oscar Carter [this message]
2020-04-18 12:36 ` [PATCH 1/2] staging: vt6656: Check the return value of vnt_control_out_* calls Oscar Carter
2020-04-18 12:36 ` [PATCH 2/2] staging: vt6656: Fix functions' documentation Oscar Carter
2020-04-18 18:05 ` Malcolm Priestley
2020-04-19 7:47 ` Oscar Carter
2020-04-19 9:22 ` Malcolm Priestley
2020-04-19 10:14 ` Oscar Carter
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=20200418123659.4475-1-oscar.carter@gmx.com \
--to=oscar.carter@gmx.com \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=indigoomega021@gmail.com \
--cc=jbwyatt4@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quentin.deslandes@itdev.co.uk \
--cc=sbrivio@redhat.com \
--cc=tvboxspy@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;
as well as URLs for NNTP newsgroup(s).