From: Felix Schlepper <f3sch.git@outlook.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Felix Schlepper <f3sch.git@outlook.com>
Subject: [PATCH v4 0/3] Staging: rtl8192e: Safer allocation and cleaner error handling
Date: Thu, 23 Jun 2022 22:27:52 +0200 [thread overview]
Message-ID: <cover.1655975970.git.f3sch.git@outlook.com> (raw)
v2:
- replaced kmalloc with kzalloc against memory initialization defects,
thus also removing a memset
- made error handling more consistent
v3:
- Split into smaller commits so that it's easier to review
v4:
- clearer commit messages
- added missing kfree
Felix Schlepper (3):
Staging: rtl8192e: Use struct_size
Staging: rtl8192e: Using kzalloc and delete memset
Staging: rtl8192e: Cleaning up error handling
drivers/staging/rtl8192e/rtllib_tx.c | 24 +++++++++++-------------
1 file changed, 11 insertions(+), 13 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-23 20:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 20:27 Felix Schlepper [this message]
2022-06-23 10:05 ` [PATCH v4 1/3] Staging: rtl8192e: Use struct_size Felix Schlepper
2022-06-23 10:05 ` [PATCH v4 2/3] Staging: rtl8192e: Using kzalloc and delete memset Felix Schlepper
2022-06-23 10:05 ` [PATCH v4 3/3] Staging: rtl8192e: Cleaning up error handling Felix Schlepper
2022-06-23 20:27 ` [PATCH v4 1/3] Staging: rtl8192e: Use struct_size Felix Schlepper
2022-06-23 20:27 ` [PATCH v4 2/3] Staging: rtl8192e: Using kzalloc and delete memset Felix Schlepper
2022-06-23 20:27 ` [PATCH v4 3/3] Staging: rtl8192e: Cleaning up error handling Felix Schlepper
2022-06-23 21:20 ` Andy Shevchenko
2022-06-24 5:21 ` Dan Carpenter
2022-06-24 8:41 ` Felix Schlepper
2022-06-24 11:32 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 10:05 [PATCH v4 0/3] Staging: rtl8192e: Safer allocation and cleaner " Felix Schlepper
2022-06-23 10:22 ` Dan Carpenter
2022-06-23 10:47 ` Greg KH
2022-06-23 13:38 ` Felix Schlepper
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=cover.1655975970.git.f3sch.git@outlook.com \
--to=f3sch.git@outlook.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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).