From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qianchang Zhao <pioooooooooip@gmail.com>, netdev@vger.kernel.org
Cc: Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Zhitong Liu <liuzhitong1993@gmail.com>
Subject: Re: [PATCH v3 0/2] nfc: llcp: fix double put/unlock on LLCP_CLOSED in recv handlers
Date: Thu, 18 Dec 2025 11:19:40 +0100 [thread overview]
Message-ID: <0d053552-35d7-4dca-ba1f-d310390194ee@kernel.org> (raw)
In-Reply-To: <20251218025923.22101-1-pioooooooooip@gmail.com>
On 18/12/2025 03:59, Qianchang Zhao wrote:
> Changes in v3:
> - Wrap commit messages to <= 75 columns
> - Use 12-char SHA in Fixes tags
> - Verify Fixes with git blame (both handlers trace back to d646960f7986)
> - Run scripts/checkpatch.pl --strict
>
Don't send new version while discussion is still going. You already did
this with v2 (twice) and now with v3.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-12-18 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 2:59 [PATCH v3 0/2] nfc: llcp: fix double put/unlock on LLCP_CLOSED in recv handlers Qianchang Zhao
2025-12-18 2:59 ` [PATCH v3 1/2] nfc: llcp: avoid double release/put on LLCP_CLOSED in nfc_llcp_recv_disc() Qianchang Zhao
2025-12-28 9:02 ` Paolo Abeni
2025-12-28 9:16 ` Paolo Abeni
2025-12-18 2:59 ` [PATCH v3 2/2] nfc: llcp: stop processing on LLCP_CLOSED in nfc_llcp_recv_hdlc() Qianchang Zhao
2025-12-18 10:19 ` Krzysztof Kozlowski [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=0d053552-35d7-4dca-ba1f-d310390194ee@kernel.org \
--to=krzk@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhitong1993@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pioooooooooip@gmail.com \
--cc=stable@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 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).