From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>
Cc: Simon Horman <horms@kernel.org>,
Konrad Leszczynski <konrad.leszczynski@intel.com>,
<davem@davemloft.net>, <andrew+netdev@lunn.ch>,
<edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<cezary.rojewski@intel.com>, <sebastian.basierski@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH net v4 1/2] net: stmmac: replace memcpy with ethtool_puts in ethtool
Date: Wed, 17 Sep 2025 08:54:58 -0700 [thread overview]
Message-ID: <ad040233-2196-4d90-9da3-326b637dedd4@intel.com> (raw)
In-Reply-To: <20250916162502.0fcdaf9a@kernel.org>
On 9/16/2025 4:25 PM, Jakub Kicinski wrote:
> On Tue, 16 Sep 2025 19:12:22 +0200 Andrew Lunn wrote:
>> where desc can be any length, ironically making
>> dwmac5_safety_feat_dump() unsafe. This is why i asked that this be
>> changed to be the same stmmac_stats, so [ETH_GSTRING_LEN]
>> __nonstring. But that seems to of fallen on deaf ears.
>
> Yes, very strange.
>
> Tony, Przemek, I suspect the folks here are from "different part of
> Intel" but I think they need some guidance..
I'll reach out and see if we can provide them some help.
Thanks,
Tony
next prev parent reply other threads:[~2025-09-17 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 12:09 [PATCH net v4 0/2] net: stmmac: misc fixes Konrad Leszczynski
2025-09-16 12:09 ` [PATCH net v4 1/2] net: stmmac: replace memcpy with ethtool_puts in ethtool Konrad Leszczynski
2025-09-16 16:45 ` Simon Horman
2025-09-16 17:12 ` Andrew Lunn
2025-09-16 23:25 ` Jakub Kicinski
2025-09-17 15:54 ` Tony Nguyen [this message]
2025-09-16 12:09 ` [PATCH net v4 2/2] net: stmmac: check if interface is running before TC block setup Konrad Leszczynski
2025-09-16 23:25 ` Jakub Kicinski
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=ad040233-2196-4d90-9da3-326b637dedd4@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=cezary.rojewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=konrad.leszczynski@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sebastian.basierski@intel.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).