From: Colin Foster <colin.foster@in-advantage.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>
Subject: Re: [PATCH v1 net 0/2] fix shared vcap_props reference
Date: Sun, 1 May 2022 14:09:10 -0700 [thread overview]
Message-ID: <20220501210910.GB590748@euler> (raw)
In-Reply-To: <20220501105208.ynlxqqt6g4oml5fz@skbuf>
On Sun, May 01, 2022 at 10:52:09AM +0000, Vladimir Oltean wrote:
> On Fri, Apr 29, 2022 at 04:30:47PM -0700, Colin Foster wrote:
> > I don't have any hardware to confidently test the vcap portions of
> > Ocelot / Felix, so any testers would be appreciated.
>
> You know about tools/testing/selftests/drivers/net/ocelot/tc_flower_chains.sh,
> right?
I'll add this to the (long) list of things you've taught / shown me.
Thanks! And thanks for testing.
prev parent reply other threads:[~2022-05-01 21:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 23:30 [PATCH v1 net 0/2] fix shared vcap_props reference Colin Foster
2022-04-29 23:30 ` [PATCH v1 net 1/2] net: ethernet: ocelot: rename vcap_props to clearly be an ocelot member Colin Foster
2022-04-30 2:07 ` Jakub Kicinski
2022-04-30 17:36 ` Colin Foster
2022-04-29 23:30 ` [PATCH v1 net 2/2] net: mscc: ocelot: fix possible memory conflict for vcap_props Colin Foster
2022-04-30 2:06 ` Jakub Kicinski
2022-04-30 17:27 ` Colin Foster
2022-04-30 14:24 ` Vladimir Oltean
2022-04-30 17:24 ` Colin Foster
2022-04-30 21:56 ` Vladimir Oltean
2022-04-30 22:26 ` Colin Foster
2022-05-01 10:52 ` [PATCH v1 net 0/2] fix shared vcap_props reference Vladimir Oltean
2022-05-01 21:09 ` Colin Foster [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=20220501210910.GB590748@euler \
--to=colin.foster@in-advantage.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.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 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.