From: Denis Efremov <denis.e.efremov@oracle.com>
To: Martin Faltesek <mfaltesek@chromium.org>,
netdev@vger.kernel.org, kuba@kernel.org, krzk@kernel.org,
christophe.ricard@gmail.com, jordy@pwning.systems
Cc: sameo@linux.intel.com, wklin@google.com, groeck@google.com,
mfaltesek@google.com, gregkh@linuxfoundation.org,
theflamefire89@gmail.com, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH v2 0/3] Split "nfc: st21nfca: Refactor EVT_TRANSACTION" into 3
Date: Thu, 2 Jun 2022 23:10:37 +0400 [thread overview]
Message-ID: <a09fa1cf-b903-75b4-0b1f-a3a3513b2c3c@oracle.com> (raw)
In-Reply-To: <20220401180939.2025819-1-mfaltesek@google.com>
Hi,
On 4/1/22 22:09, Martin Faltesek wrote:
> Changes in v2:
> -- Split the original patch into 3 patches, so that each one solves
> a single issue. The original patch indicated 4 bugs, but two are
> so closely related that I feel it makes sense to keep them
> together.
>
> -- 1/3
> nfc: st21nfca: fix incorrect validating logic in EVT_TRANSACTION
>
> This is mentioned in v1 as #1. It just changes logical AND to
> logical OR. The AND was rendering the check useless.
>
> -- 2/3
> nfc: st21nfca: fix memory leaks in EVT_TRANSACTION handling
>
> This is from v1 #3.
>
> -- 3/3
> nfc: st21nfca: fix incorrect sizing calculations in EVT_TRANSACTION
>
> This is from v1 #2 and #4
> Both are derived from the same bug, which is the incorrect calculation
> that buffer allocation size is skb->len - 2, so both should be combined.
>
> After these 3 patches are applied, the end result is the same as v1
> except:
>
> -- minor comment rewording.
> -- removed some comments which felt superfluous explanations of
> obvious code.
>
> Martin Faltesek (3):
> nfc: st21nfca: fix incorrect validating logic in EVT_TRANSACTION
> nfc: st21nfca: fix memory leaks in EVT_TRANSACTION handling
> nfc: st21nfca: fix incorrect sizing calculations in EVT_TRANSACTION
>
> drivers/nfc/st21nfca/se.c | 51 +++++++++++++++++++++++----------------
> 1 file changed, 30 insertions(+), 21 deletions(-)
>
Ping?
Denis
prev parent reply other threads:[~2022-06-02 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 18:09 [PATCH v2 0/3] Split "nfc: st21nfca: Refactor EVT_TRANSACTION" into 3 Martin Faltesek
2022-04-02 9:07 ` Krzysztof Kozlowski
2022-06-02 19:10 ` Denis Efremov [this message]
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=a09fa1cf-b903-75b4-0b1f-a3a3513b2c3c@oracle.com \
--to=denis.e.efremov@oracle.com \
--cc=christophe.ricard@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@google.com \
--cc=jordy@pwning.systems \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=mfaltesek@chromium.org \
--cc=mfaltesek@google.com \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sameo@linux.intel.com \
--cc=theflamefire89@gmail.com \
--cc=wklin@google.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).