From: Michael Walle <michael@walle.cc>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Charles Gorand" <charles.gorand@effinnov.com>,
"Clément Perrochaud" <clement.perrochaud@nxp.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] NFC: nxp-nci: check return code of i2c_master_recv()
Date: Sun, 26 Jun 2022 21:55:16 +0200 [thread overview]
Message-ID: <cd4780159ec9a66b417c4f1fb50d288c@walle.cc> (raw)
In-Reply-To: <99e3ad4f-077a-0ca0-6842-b0c5a3439b68@linaro.org>
Am 2022-06-26 21:49, schrieb Krzysztof Kozlowski:
> On 26/06/2022 21:42, Michael Walle wrote:
>> Check the return code of i2c_master_recv() for actual errors and
>> propagate it to the caller.
>>
>> Fixes: 6be88670fc59 ("NFC: nxp-nci_i2c: Add I2C support to NXP NCI
>> driver")
>
> The check was there, so I don't see here bug. The only thing missing
> was
> a bit more detailed error message (without cast to %u) and propagating
> error code instead of EBADMSG, but these are not bugs. The commit msg
> should sound different and Fixes tag is not appropriate.
Well one could argue the nfc_err() is very misleading as it prints
an unreasonable large number. Will remove the Fixes tag and reword
the commit message.
>> Signed-off-by: Michael Walle <michael@walle.cc>
>> ---
>> drivers/nfc/nxp-nci/i2c.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/nfc/nxp-nci/i2c.c b/drivers/nfc/nxp-nci/i2c.c
>> index 7e451c10985d..9c80d5a6d56b 100644
>> --- a/drivers/nfc/nxp-nci/i2c.c
>> +++ b/drivers/nfc/nxp-nci/i2c.c
>> @@ -163,7 +163,10 @@ static int nxp_nci_i2c_nci_read(struct
>> nxp_nci_i2c_phy *phy,
>> skb_put_data(*skb, (void *)&header, NCI_CTRL_HDR_SIZE);
>>
>> r = i2c_master_recv(client, skb_put(*skb, header.plen),
>> header.plen);
>> - if (r != header.plen) {
>> + if (r < 0) {
>> + nfc_err(&client->dev, "I2C receive error %pe\n", ERR_PTR(r));
>
> Print just 'r'.
Personally, I prefer seeing the actual error string and this idiom is
also used in other drivers. But I wont insist, will change it.
>
>> + goto nci_read_exit_free_skb;
>> + } else if (r != header.plen) {
>> nfc_err(&client->dev,
>> "Invalid frame payload length: %u (expected %u)\n",
>> r, header.plen);
>
>
> Best regards,
> Krzysztof
-michael
prev parent reply other threads:[~2022-06-26 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 19:42 Michael Walle
2022-06-26 19:42 ` [PATCH 2/2] NFC: nxp-nci: Don't issue a zero length i2c_master_read() Michael Walle
2022-06-26 19:51 ` Krzysztof Kozlowski
2022-06-26 19:56 ` Michael Walle
2022-06-26 20:02 ` Krzysztof Kozlowski
2022-06-28 5:03 ` Jakub Kicinski
2022-06-28 6:42 ` Michael Walle
2022-06-26 19:49 ` [PATCH 1/2] NFC: nxp-nci: check return code of i2c_master_recv() Krzysztof Kozlowski
2022-06-26 19:55 ` Michael Walle [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=cd4780159ec9a66b417c4f1fb50d288c@walle.cc \
--to=michael@walle.cc \
--cc=charles.gorand@effinnov.com \
--cc=clement.perrochaud@nxp.com \
--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
all inboxes | Powered by JetHome®