From: duoming@zju.edu.cn
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net] NFC: hci: fix sleep in atomic context bugs in nfc_hci_hcp_message_tx
Date: Tue, 17 May 2022 20:24:35 +0800 (GMT+08:00) [thread overview]
Message-ID: <147574ae.199bb.180d1fa2bba.Coremail.duoming@zju.edu.cn> (raw)
In-Reply-To: <171c13bb-9fc9-0807-e872-6859dfa2603d@linaro.org>
Hello,
On Tue, 17 May 2022 13:39:44 +0200 wrote:
> You sent v2 one minute before replying here... that's not how discussion
> work. Please do not sent next version before reaching some consensus.
I am sorry. Before reaching some consensus, I will not send next version in the future.
Thanks for your guidance.
Best regards,
Duoming Zhou
prev parent reply other threads:[~2022-05-17 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 2:10 [PATCH net] NFC: hci: fix sleep in atomic context bugs in nfc_hci_hcp_message_tx Duoming Zhou
2022-05-16 6:44 ` Krzysztof Kozlowski
2022-05-16 10:18 ` duoming
2022-05-16 10:43 ` Krzysztof Kozlowski
2022-05-17 10:56 ` duoming
2022-05-17 11:39 ` Krzysztof Kozlowski
2022-05-17 12:24 ` duoming [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=147574ae.199bb.180d1fa2bba.Coremail.duoming@zju.edu.cn \
--to=duoming@zju.edu.cn \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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