All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Michael Walle <michael@walle.cc>
Cc: krzysztof.kozlowski@linaro.org, clement.perrochaud@nxp.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] NFC: nxp-nci: Don't issue a zero length i2c_master_read()
Date: Wed, 29 Jun 2022 13:10:15 +0000	[thread overview]
Message-ID: <165650821524.20617.14794992816689313521.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220627170643.98239-1-michael@walle.cc>

Hello:

This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 27 Jun 2022 19:06:42 +0200 you wrote:
> There are packets which doesn't have a payload. In that case, the second
> i2c_master_read() will have a zero length. But because the NFC
> controller doesn't have any data left, it will NACK the I2C read and
> -ENXIO will be returned. In case there is no payload, just skip the
> second i2c master read.
> 
> Fixes: 6be88670fc59 ("NFC: nxp-nci_i2c: Add I2C support to NXP NCI driver")
> Signed-off-by: Michael Walle <michael@walle.cc>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> 
> [...]

Here is the summary with links:
  - [v2,1/2] NFC: nxp-nci: Don't issue a zero length i2c_master_read()
    https://git.kernel.org/netdev/net/c/eddd95b94239
  - [v2,2/2] NFC: nxp-nci: don't print header length mismatch on i2c error
    https://git.kernel.org/netdev/net/c/9577fc5fdc8b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-06-29 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 17:06 [PATCH v2 1/2] NFC: nxp-nci: Don't issue a zero length i2c_master_read() Michael Walle
2022-06-27 17:06 ` [PATCH v2 2/2] NFC: nxp-nci: don't print header length mismatch on i2c error Michael Walle
2022-06-29  9:21   ` Krzysztof Kozlowski
2022-06-29 13:10 ` patchwork-bot+netdevbpf [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=165650821524.20617.14794992816689313521.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=clement.perrochaud@nxp.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --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 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.