From: Jakub Kicinski <kuba@kernel.org>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: mustafa.ismail@intel.com, leon@kernel.org,
benjamin.mikailenko@intel.com, jesse.brandeburg@intel.com,
leszek.kaliszczuk@intel.com, netdev@vger.kernel.org,
przemyslaw.kitszel@intel.com, intel-wired-lan@lists.osuosl.org,
shiraz.saleem@intel.com
Subject: Re: [Intel-wired-lan] [PATCH net-next v1 00/10] implement devlink reload in ice
Date: Tue, 13 Dec 2022 17:18:34 -0800 [thread overview]
Message-ID: <20221213171834.682641c3@kernel.org> (raw)
In-Reply-To: <Y5gdpoif/1zBUKDB@localhost.localdomain>
On Tue, 13 Dec 2022 07:37:26 +0100 Michal Swiatkowski wrote:
> It was targeted to Tony dev-queue to allow some tests as Jake said.
> Sorry, probably I should point it out in cover letter.
You can tag as intel-next, iwl-next or some such, to avoid confusion.
_______________________________________________
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: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: Jacob Keller <jacob.e.keller@intel.com>,
intel-wired-lan@lists.osuosl.org, alexandr.lobakin@intel.com,
sridhar.samudrala@intel.com, wojciech.drewek@intel.com,
lukasz.czapnik@intel.com, shiraz.saleem@intel.com,
jesse.brandeburg@intel.com, mustafa.ismail@intel.com,
przemyslaw.kitszel@intel.com, piotr.raczynski@intel.com,
david.m.ertman@intel.com, leszek.kaliszczuk@intel.com,
benjamin.mikailenko@intel.com, paul.m.stillwell.jr@intel.com,
netdev@vger.kernel.org, leon@kernel.org
Subject: Re: [PATCH net-next v1 00/10] implement devlink reload in ice
Date: Tue, 13 Dec 2022 17:18:34 -0800 [thread overview]
Message-ID: <20221213171834.682641c3@kernel.org> (raw)
In-Reply-To: <Y5gdpoif/1zBUKDB@localhost.localdomain>
On Tue, 13 Dec 2022 07:37:26 +0100 Michal Swiatkowski wrote:
> It was targeted to Tony dev-queue to allow some tests as Jake said.
> Sorry, probably I should point it out in cover letter.
You can tag as intel-next, iwl-next or some such, to avoid confusion.
next prev parent reply other threads:[~2022-12-14 1:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:16 [Intel-wired-lan] [PATCH net-next v1 00/10] implement devlink reload in ice Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 01/10] ice: move RDMA init to ice_idc.c Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 02/10] ice: alloc id for RDMA using xa_array Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 03/10] ice: cleanup in VSI config/deconfig code Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 04/10] ice: split ice_vsi_setup into smaller functions Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 05/10] ice: stop hard coding the ICE_VSI_CTRL location Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 06/10] ice: split probe into smaller functions Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 07/10] ice: sync netdev filters after clearing VSI Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 08/10] ice: move VSI delete outside deconfig Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 09/10] ice: update VSI instead of init in some case Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 11:16 ` [Intel-wired-lan] [PATCH net-next v1 10/10] ice: implement devlink reinit action Michal Swiatkowski
2022-12-12 11:16 ` Michal Swiatkowski
2022-12-12 18:15 ` [Intel-wired-lan] [PATCH net-next v1 00/10] implement devlink reload in ice Jakub Kicinski
2022-12-12 18:15 ` Jakub Kicinski
2022-12-12 18:46 ` [Intel-wired-lan] " Jacob Keller
2022-12-12 18:46 ` Jacob Keller
2022-12-13 6:37 ` [Intel-wired-lan] " Michal Swiatkowski
2022-12-13 6:37 ` Michal Swiatkowski
2022-12-14 1:18 ` Jakub Kicinski [this message]
2022-12-14 1:18 ` Jakub Kicinski
2022-12-15 6:42 ` [Intel-wired-lan] " Michal Swiatkowski
2022-12-15 6:42 ` Michal Swiatkowski
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=20221213171834.682641c3@kernel.org \
--to=kuba@kernel.org \
--cc=benjamin.mikailenko@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=leon@kernel.org \
--cc=leszek.kaliszczuk@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=shiraz.saleem@intel.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.