Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2 1/2] NFC: nxp-nci: Don't issue a zero length
 i2c_master_read()
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <165650821524.20617.14794992816689313521.git-patchwork-notify@kernel.org>
Date:   Wed, 29 Jun 2022 13:10:15 +0000
References: <20220627170643.98239-1-michael@walle.cc>
In-Reply-To: <20220627170643.98239-1-michael@walle.cc>
To:     Michael Walle <michael@walle.cc>
Cc:     krzysztof.kozlowski@linaro.org, clement.perrochaud@nxp.com,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Precedence: bulk

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