From: Jakub Kicinski <kuba@kernel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
Cc: "jiri@resnulli.us" <jiri@resnulli.us>,
"corbet@lwn.net" <corbet@lwn.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [RFC PATCH v1] ice: add CGU info to devlink info callback
Date: Fri, 14 Apr 2023 07:46:37 -0700 [thread overview]
Message-ID: <20230414074637.561010cc@kernel.org> (raw)
In-Reply-To: <DM6PR11MB4657EF2201A5E110697C9E129B999@DM6PR11MB4657.namprd11.prod.outlook.com>
On Fri, 14 Apr 2023 10:04:05 +0000 Kubalewski, Arkadiusz wrote:
> Although I double checked, and it seems I wasn't clear on previous explanation.
> Once FW update is possible with Intel's nvmupdate tools, the devlink FW update
> also going to update CGU firmware (part of nvm-flash region), so after all this
> seems a right place for this info.
👍️
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
Cc: "jiri@resnulli.us" <jiri@resnulli.us>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [RFC PATCH v1] ice: add CGU info to devlink info callback
Date: Fri, 14 Apr 2023 07:46:37 -0700 [thread overview]
Message-ID: <20230414074637.561010cc@kernel.org> (raw)
In-Reply-To: <DM6PR11MB4657EF2201A5E110697C9E129B999@DM6PR11MB4657.namprd11.prod.outlook.com>
On Fri, 14 Apr 2023 10:04:05 +0000 Kubalewski, Arkadiusz wrote:
> Although I double checked, and it seems I wasn't clear on previous explanation.
> Once FW update is possible with Intel's nvmupdate tools, the devlink FW update
> also going to update CGU firmware (part of nvm-flash region), so after all this
> seems a right place for this info.
👍️
next prev parent reply other threads:[~2023-04-14 14:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 13:38 [Intel-wired-lan] [RFC PATCH v1] ice: add CGU info to devlink info callback Arkadiusz Kubalewski
2023-04-12 13:38 ` Arkadiusz Kubalewski
2023-04-12 21:33 ` [Intel-wired-lan] " Jacob Keller
2023-04-13 13:36 ` Kubalewski, Arkadiusz
2023-04-13 16:42 ` Jacob Keller
2023-04-14 12:34 ` Kubalewski, Arkadiusz
2023-04-13 3:35 ` Jakub Kicinski
2023-04-13 3:35 ` Jakub Kicinski
2023-04-13 13:43 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-04-13 13:43 ` Kubalewski, Arkadiusz
2023-04-13 15:04 ` [Intel-wired-lan] " Jakub Kicinski
2023-04-13 15:04 ` Jakub Kicinski
2023-04-14 10:04 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-04-14 10:04 ` Kubalewski, Arkadiusz
2023-04-14 14:46 ` Jakub Kicinski [this message]
2023-04-14 14:46 ` Jakub Kicinski
2023-04-13 13:17 ` [Intel-wired-lan] " Leon Romanovsky
2023-04-13 13:17 ` Leon Romanovsky
2023-04-13 14:04 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-04-13 14:04 ` Kubalewski, Arkadiusz
2023-04-13 17:17 ` [Intel-wired-lan] " Leon Romanovsky
2023-04-13 17:17 ` Leon Romanovsky
2023-04-14 10:06 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-04-14 10:06 ` Kubalewski, Arkadiusz
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=20230414074637.561010cc@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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.