From: "Arinzon, David" <darinzon@amazon.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"Machulsky, Zorik" <zorik@amazon.com>,
"Matushevsky, Alexander" <matua@amazon.com>,
"Bshara, Saeed" <saeedb@amazon.com>,
"Wilson, Matt" <msw@amazon.com>,
"Liguori, Anthony" <aliguori@amazon.com>,
"Bshara, Nafea" <nafea@amazon.com>,
"Schmeilin, Evgeny" <evgenys@amazon.com>,
"Belgazal, Netanel" <netanel@amazon.com>,
"Saidi, Ali" <alisaidi@amazon.com>,
"Herrenschmidt, Benjamin" <benh@amazon.com>,
"Kiyanovski, Arthur" <akiyano@amazon.com>,
"Dagan, Noam" <ndagan@amazon.com>,
"Bernstein, Amit" <amitbern@amazon.com>,
"Allen, Neil" <shayagr@amazon.com>,
"Ostrovsky, Evgeny" <evostrov@amazon.com>,
"Tabachnik, Ofir" <ofirt@amazon.com>,
"Machnikowski, Maciek" <maciek@machnikowski.net>,
Rahul Rameshbabu <rrameshbabu@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Andrew Lunn <andrew@lunn.ch>, Leon Romanovsky <leon@kernel.org>
Subject: RE: [PATCH v10 net-next 4/8] net: ena: Control PHC enable through devlink
Date: Thu, 22 May 2025 14:22:21 +0000 [thread overview]
Message-ID: <11eaa373bb894946bc693d9a1e112ca5@amazon.com> (raw)
In-Reply-To: <aq5z7dmgtdvdut437b3r3jfhevzfhknf5zr5obaunadp2xkzsh@iene76rtx3xc>
> [...]
>
>
> >+enum ena_devlink_param_id {
> >+ ENA_DEVLINK_PARAM_ID_BASE =
> DEVLINK_PARAM_GENERIC_ID_MAX,
> >+ ENA_DEVLINK_PARAM_ID_PHC_ENABLE,
>
> What exactly is driver/vendor specific about this? Sounds quite generic to
> me.
Can you please clarify the question?
If you refer to the need of ENA_DEVLINK_PARAM_ID_PHC_ENABLE, it was discussed as part of patchset v8 in https://lore.kernel.org/netdev/20250304190504.3743-6-darinzon@amazon.com/
More specifically in https://lore.kernel.org/netdev/55f9df6241d052a91dfde950af04c70969ea28b2.camel@infradead.org/
next prev parent reply other threads:[~2025-05-22 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 13:48 [PATCH v10 net-next 0/8] PHC support in ENA driver David Arinzon
2025-05-22 13:48 ` [PATCH v10 net-next 1/8] net: ena: Add PHC support in the " David Arinzon
2025-05-22 13:48 ` [PATCH v10 net-next 2/8] net: ena: PHC silent reset David Arinzon
2025-05-22 13:48 ` [PATCH v10 net-next 3/8] net: ena: Add device reload capability through devlink David Arinzon
2025-05-22 13:48 ` [PATCH v10 net-next 4/8] net: ena: Control PHC enable " David Arinzon
2025-05-22 13:57 ` Jiri Pirko
2025-05-22 14:22 ` Arinzon, David [this message]
2025-05-22 14:33 ` Jiri Pirko
2025-05-22 14:55 ` Arinzon, David
2025-05-22 15:39 ` Jiri Pirko
2025-05-22 16:07 ` Arinzon, David
2025-05-22 13:48 ` [PATCH v10 net-next 5/8] net: ena: Add debugfs support to the ENA driver David Arinzon
2025-05-22 13:48 ` [PATCH v10 net-next 6/8] net: ena: View PHC stats using debugfs David Arinzon
2025-05-22 13:48 ` [PATCH v10 net-next 7/8] net: ena: Add PHC documentation David Arinzon
2025-05-22 13:48 ` [PATCH v10 net-next 8/8] net: ena: Add a DEVLINK readme David Arinzon
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=11eaa373bb894946bc693d9a1e112ca5@amazon.com \
--to=darinzon@amazon.com \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=amitbern@amazon.com \
--cc=andrew@lunn.ch \
--cc=benh@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.co.uk \
--cc=edumazet@google.com \
--cc=evgenys@amazon.com \
--cc=evostrov@amazon.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=maciek@machnikowski.net \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=ofirt@amazon.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedb@amazon.com \
--cc=shayagr@amazon.com \
--cc=vadim.fedorenko@linux.dev \
--cc=zorik@amazon.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.