From: Quentin Lambert <lambert.quentin@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org
Subject: [PATCH v2 0/2] add missing calls to kfree
Date: Fri, 12 Aug 2016 14:15:16 +0000 [thread overview]
Message-ID: <20160812141518.12585-1-lambert.quentin@gmail.com> (raw)
The first patch is a style fix, the second add calls to kfree.
The reason for me thinking that they are necessary is that every other branches
leading to an error return are jumping to the same destination.
v2: add a commit message to the first patch
---
drivers/staging/rts5208/ms.c | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
---
WARNING: multiple messages have this Message-ID (diff)
From: Quentin Lambert <lambert.quentin@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org
Subject: [PATCH v2 0/2] add missing calls to kfree
Date: Fri, 12 Aug 2016 16:15:16 +0200 [thread overview]
Message-ID: <20160812141518.12585-1-lambert.quentin@gmail.com> (raw)
The first patch is a style fix, the second add calls to kfree.
The reason for me thinking that they are necessary is that every other branches
leading to an error return are jumping to the same destination.
v2: add a commit message to the first patch
---
drivers/staging/rts5208/ms.c | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
---
next reply other threads:[~2016-08-12 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 14:15 Quentin Lambert [this message]
2016-08-12 14:15 ` [PATCH v2 0/2] add missing calls to kfree Quentin Lambert
2016-08-12 14:15 ` [PATCH v2 1/2] staging: rts5208/ms.c: change the label name to respect the coding style Quentin Lambert
2016-08-12 14:15 ` Quentin Lambert
2016-08-12 14:15 ` [PATCH v2 2/2] staging: rts5208/ms.c: add missing releases in mg_get_local_EKB and mg_get_ICV Quentin Lambert
2016-08-12 14:15 ` Quentin Lambert
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=20160812141518.12585-1-lambert.quentin@gmail.com \
--to=lambert.quentin@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--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.