From: Simon Horman <horms@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Subject: Re: [ANN] netdev call - Nov 21st
Date: Tue, 21 Nov 2023 16:05:42 +0000 [thread overview]
Message-ID: <20231121160542.GA1136838@kernel.org> (raw)
In-Reply-To: <20231120082805.35527339@kernel.org>
On Mon, Nov 20, 2023 at 08:28:05AM -0800, Jakub Kicinski wrote:
> Hi,
>
> The bi-weekly netdev call at https://bbb.lwn.net/b/jak-wkr-seg-hjn
> is scheduled tomorrow at 8:30 am (PT) / 5:30 pm (~EU).
>
> So far the only agenda item is a minor update on CI,
> please send other topics!
Hi Jakub, all,
I would like to ask about the preferred mechanism for drivers
to dump state information from firmware to user-space.
I recall that at least for the NFP driver this was implemented
using ethtool -w/-W. But that was some time ago and I'd like
to understand if that is still the preferred method.
next prev parent reply other threads:[~2023-11-21 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 16:28 [Intel-wired-lan] [ANN] netdev call - Nov 21st Jakub Kicinski
2023-11-20 16:28 ` Jakub Kicinski
2023-11-21 16:05 ` Simon Horman [this message]
2023-11-21 17:11 ` Jakub Kicinski
2023-11-23 14:15 ` Simon Horman
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=20231121160542.GA1136838@kernel.org \
--to=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.