From: Jiri Pirko <jiri@resnulli.us>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
jiri@nvidia.com
Subject: Re: [PATCH net-next 0/2] devlink: add params FW_BANK and ENABLE_MIGRATION
Date: Wed, 7 Dec 2022 14:32:05 +0100 [thread overview]
Message-ID: <Y5CV1UUTCboipF7E@nanopsycho> (raw)
In-Reply-To: <b916302e-8654-2e00-0618-0a2cb8fc757c@amd.com>
Tue, Dec 06, 2022 at 07:21:24PM CET, shannon.nelson@amd.com wrote:
>On 12/6/22 1:00 AM, Jiri Pirko wrote:
>> Mon, Dec 05, 2022 at 06:26:25PM CET, shannon.nelson@amd.com wrote:
>> > Some discussions of a recent new driver RFC [1] suggested that these
>> > new parameters would be a good addition to the generic devlink list.
>> > If accepted, they will be used in the next version of the discussed
>> > driver patchset.
>> >
>> > [1] https://lore.kernel.org/netdev/20221118225656.48309-11-snelson@pensando.io/
>> >
>> > Shannon Nelson (2):
>> > devlink: add fw bank select parameter
>> > devlink: add enable_migration parameter
>>
>> Where's the user? You need to introduce it alongside in this patchset.
>
>I'll put them at the beginning of the next version of the pds_core patchset.
You need to do it in a single patchset, if possible. Here, I believe it
is possible easily.
>
>
>>
>> >
>> > Documentation/networking/devlink/devlink-params.rst | 8 ++++++++
>> > include/net/devlink.h | 8 ++++++++
>> > net/core/devlink.c | 10 ++++++++++
>> > 3 files changed, 26 insertions(+)
>> >
>> > --
>> > 2.17.1
>> >
prev parent reply other threads:[~2022-12-07 13:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 17:26 [PATCH net-next 0/2] devlink: add params FW_BANK and ENABLE_MIGRATION Shannon Nelson
2022-12-05 17:26 ` [PATCH net-next 1/2] devlink: add fw bank select parameter Shannon Nelson
2022-12-06 9:07 ` Jiri Pirko
2022-12-06 18:18 ` Shannon Nelson
2022-12-07 13:34 ` Jiri Pirko
2022-12-07 1:41 ` Jakub Kicinski
2022-12-07 19:29 ` Shannon Nelson
2022-12-08 0:36 ` Jakub Kicinski
2022-12-08 18:44 ` Shannon Nelson
2022-12-09 0:47 ` Jacob Keller
2022-12-09 1:24 ` Jakub Kicinski
2022-12-12 18:04 ` Jacob Keller
2022-12-12 18:34 ` Jakub Kicinski
2022-12-09 1:15 ` Jakub Kicinski
2022-12-05 17:26 ` [PATCH net-next 2/2] devlink: add enable_migration parameter Shannon Nelson
2022-12-06 9:04 ` Jiri Pirko
2022-12-06 18:28 ` Shannon Nelson
2022-12-07 13:33 ` Jiri Pirko
2022-12-05 18:22 ` [PATCH net-next 0/2] devlink: add params FW_BANK and ENABLE_MIGRATION Leon Romanovsky
2022-12-05 18:55 ` Shannon Nelson
2022-12-06 8:13 ` Leon Romanovsky
2022-12-06 9:00 ` Jiri Pirko
2022-12-06 18:21 ` Shannon Nelson
2022-12-07 13:32 ` Jiri Pirko [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=Y5CV1UUTCboipF7E@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.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).