From: Jakub Kicinski <kuba@kernel.org>
To: Naveen Mamindlapalli <naveenm@marvell.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<horms@kernel.org>, <corbet@lwn.net>, <andrew@lunn.ch>,
<netdev@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] docs: networking: clarify expectation of persistent stats
Date: Fri, 5 Sep 2025 16:07:20 -0700 [thread overview]
Message-ID: <20250905160720.1e7b2136@kernel.org> (raw)
In-Reply-To: <aLrDvpAsVq4vTytH@naveenm-PowerEdge-T630>
On Fri, 5 Sep 2025 16:34:30 +0530 Naveen Mamindlapalli wrote:
> > Note that the following legacy drivers do not comply with this requirement
> > and cannot be fixed without breaking existing users:
> > - driver1
> > - driver2
> > ...
> I don’t have a definitive list of non-compliant drivers. Would you prefer to add
> a brief note stating that some drivers may not comply, without naming them explicitly?
We don't have to list them all from the start.
It's for a quick sanity check so that users don't duplicate work
validating that their driver is broken. Maybe say ".. following legacy
drivers are known not to comply .." Hopefully the "are known"
sufficiently indicates that we're covering only one quadrant of
the Rumsfeld matrix.
prev parent reply other threads:[~2025-09-05 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 13:47 [PATCH net-next] docs: networking: clarify expectation of persistent stats Naveen Mamindlapalli
2025-08-27 0:44 ` Jakub Kicinski
2025-09-05 11:04 ` Naveen Mamindlapalli
2025-09-05 23:07 ` Jakub Kicinski [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=20250905160720.1e7b2136@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--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 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.