From: SF Markus Elfring <elfring@users.sourceforge.net>
To: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Maciek Borzecki <maciek.borzecki@gmail.com>,
Simo Koskinen <koskisoft@gmail.com>,
Thibaut Sautereau <thibaut.sautereau@telecom-sudparis.eu>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/4] staging/wlan-ng/prism2fw: Adjustments for two function implementations
Date: Wed, 13 Dec 2017 14:10:31 +0100 [thread overview]
Message-ID: <3599ae76-1aa8-4b6a-bf31-90e467759629@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Wed, 13 Dec 2017 14:03:02 +0100
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Delete an error message for a failed memory allocation in mkimage()
Use a known error code after a failed kzalloc() in mkimage()
Delete an error message for a failed memory allocation in writeimage()
Use common error handling code in writeimage()
drivers/staging/wlan-ng/prism2fw.c | 15 +++++----------
1 file changed, 5 insertions(+), 10 deletions(-)
--
2.15.1
next reply other threads:[~2017-12-13 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 13:10 SF Markus Elfring [this message]
2017-12-13 13:11 ` [PATCH 1/4] staging/wlan-ng/prism2fw: Delete an error message for a failed memory allocation in mkimage() SF Markus Elfring
2017-12-13 13:12 ` [PATCH 2/4] staging/wlan-ng/prism2fw: Use a known error code after a failed kzalloc() " SF Markus Elfring
2017-12-13 13:13 ` [PATCH 3/4] staging/wlan-ng/prism2fw: Delete an error message for a failed memory allocation in writeimage() SF Markus Elfring
2017-12-13 13:14 ` [PATCH 4/4] staging/wlan-ng/prism2fw: Use common error handling code " SF Markus Elfring
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=3599ae76-1aa8-4b6a-bf31-90e467759629@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=koskisoft@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciek.borzecki@gmail.com \
--cc=thibaut.sautereau@telecom-sudparis.eu \
/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
all inboxes | Powered by JetHome®