From: Vladimir Oltean <olteanv@gmail.com>
To: Jerry Ray <jerry.ray@microchip.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
jbe@pengutronix.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk
Subject: Re: [PATCH v2] net: lan9303: Fix read error execution path
Date: Fri, 9 Dec 2022 19:05:50 +0200 [thread overview]
Message-ID: <20221209170550.o3pro2tx5n6lh7pa@skbuf> (raw)
In-Reply-To: <20221209153502.7429-1-jerry.ray@microchip.com>
On Fri, Dec 09, 2022 at 09:35:02AM -0600, Jerry Ray wrote:
> This patch fixes an issue where a read failure of a port statistic counter
> will return unknown results. While it is highly unlikely the read will
> ever fail, it is much cleaner to return a zero for the stat count.
>
> Fixes: a1292595e006 ("net: dsa: add new DSA switch driver for the SMSC-LAN9303")
> Signed-off-by: Jerry Ray <jerry.ray@microchip.com>
> ---
> v1->v2:
> corrected email header: net vs net-next, Added 1 maintainer, removed
> blank line.
Actually it's not "net vs net-next", but rather, "nothing vs net-next".
As you can see, the patchwork CI complains that "Target tree name [is]
not specified in the subject".
https://patchwork.kernel.org/project/netdevbpf/patch/20221209153502.7429-1-jerry.ray@microchip.com/
Anyway, I think it's quite obvious for maintainers that it's a patch
intended for the net.git tree, so there isn't a reason to resend this
patch, just something to know and to do better in the future.
> No changes to the body of the patch.
> ---
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
next prev parent reply other threads:[~2022-12-09 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 15:35 Jerry Ray
2022-12-09 17:05 ` Vladimir Oltean [this message]
2022-12-09 17:08 ` Florian Fainelli
2022-12-12 21:00 ` patchwork-bot+netdevbpf
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=20221209170550.o3pro2tx5n6lh7pa@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jbe@pengutronix.de \
--cc=jerry.ray@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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®