From: Saeed Mahameed <saeed@kernel.org>
To: netdev@kapio-technology.com
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
netdev@vger.kernel.org, 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>
Subject: Re: [PATCH net-next 2/3] net: dsa: mv88e6xxx: replace ATU violation prints with trace points
Date: Thu, 8 Dec 2022 16:26:50 -0800 [thread overview]
Message-ID: <Y5KAyrdaL7qU/J+e@x130> (raw)
In-Reply-To: <78b2412528dae7225d280a904a38bd67@kapio-technology.com>
On 08 Dec 16:35, netdev@kapio-technology.com wrote:
>On 2022-12-08 16:27, Vladimir Oltean wrote:
>>On Thu, Dec 08, 2022 at 04:22:53PM +0100,
>>netdev@kapio-technology.com wrote:
>>>The follow-up patch set to the MAB patch set I have, will make use
>>>of the age
>>>out violation.
>>
>>Ok, so for v2 I can delete the debugging print, since it's currently
>>dead code, and you can add the counter and the trace point when the
>>code
>>will be actually exercised, how does that sound?
>
>Ok, sounds like a plan.
FWIW +1 :)
next prev parent reply other threads:[~2022-12-09 0:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 23:39 [PATCH net-next 0/3] Trace points for mv88e6xxx Vladimir Oltean
2022-12-07 23:39 ` [PATCH net-next 1/3] net: dsa: mv88e6xxx: read FID when handling ATU violations Vladimir Oltean
2022-12-07 23:39 ` [PATCH net-next 2/3] net: dsa: mv88e6xxx: replace ATU violation prints with trace points Vladimir Oltean
2022-12-08 0:14 ` Saeed Mahameed
2022-12-08 14:49 ` Vladimir Oltean
2022-12-08 15:22 ` netdev
2022-12-08 15:27 ` Vladimir Oltean
2022-12-08 15:35 ` netdev
2022-12-09 0:26 ` Saeed Mahameed [this message]
2022-12-08 18:33 ` netdev
2022-12-08 19:31 ` Vladimir Oltean
2022-12-07 23:39 ` [PATCH net-next 3/3] net: dsa: mv88e6xxx: replace VTU " Vladimir Oltean
2022-12-08 12:32 ` [PATCH net-next 0/3] Trace points for mv88e6xxx netdev
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=Y5KAyrdaL7qU/J+e@x130 \
--to=saeed@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@kapio-technology.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).