From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Colin Foster <colin.foster@in-advantage.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>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Vladimir Oltean <olteanv@gmail.com>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH v1 net-next 1/2] net: mscc: ocelot: remove redundant stats_layout pointers
Date: Tue, 15 Nov 2022 17:39:43 +0000 [thread overview]
Message-ID: <20221115173942.mdn2r3i6joehhohu@skbuf> (raw)
In-Reply-To: <Y3PIIQeGD9LUs2np@colin-ia-desktop>
On Tue, Nov 15, 2022 at 09:10:57AM -0800, Colin Foster wrote:
> That should work. If there end up being 10 different struct
> ocelot_stat_layout[]s, we might reconsider... but in the foreseeable
> future there will only be two.
>
> So this applies to patch 2 of my set, which means I'll pretty much keep
> it as-is. The get_stats_layout and the ocelot_mm_stats_layout can be
> added when the 9959 stuff gets applied.
Sounds good.
next prev parent reply other threads:[~2022-11-15 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 20:49 [PATCH v1 net-next 0/2] cleanup ocelot_stats exposure Colin Foster
2022-11-11 20:49 ` [PATCH v1 net-next 1/2] net: mscc: ocelot: remove redundant stats_layout pointers Colin Foster
2022-11-12 1:08 ` kernel test robot
2022-11-12 18:05 ` Colin Foster
2022-11-14 15:15 ` Vladimir Oltean
2022-11-15 3:43 ` Colin Foster
2022-11-15 16:08 ` Vladimir Oltean
2022-11-15 17:10 ` Colin Foster
2022-11-15 17:39 ` Vladimir Oltean [this message]
2022-11-11 20:49 ` [PATCH v1 net-next 2/2] net: mscc: ocelot: remove unnecessary exposure of stats structures Colin Foster
2022-11-12 10:34 ` kernel test robot
2022-11-14 15:19 ` Vladimir Oltean
2022-11-15 3:47 ` Colin Foster
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=20221115173942.mdn2r3i6joehhohu@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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