From: Jakub Kicinski <kuba@kernel.org>
To: "Nikolova, Tatyana E" <tatyana.e.nikolova@intel.com>
Cc: "jgg@nvidia.com" <jgg@nvidia.com>,
"leon@kernel.org" <leon@kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [iwl-next v5 0/5] Refactor to prepare for Intel IPU E2000 (GEN3)
Date: Thu, 24 Apr 2025 14:51:28 -0700 [thread overview]
Message-ID: <20250424145128.60467c51@kernel.org> (raw)
In-Reply-To: <IA1PR11MB7727AF19E37851E3A4964C77CB852@IA1PR11MB7727.namprd11.prod.outlook.com>
On Thu, 24 Apr 2025 15:58:56 +0000 Nikolova, Tatyana E wrote:
> Would you be able to review this updated patch series?
>
> Netdev maintainers,
>
> Based on Leon's previous comment https://lore.kernel.org/all/20250216111800.GV17863@unreal/, he would like to get acks on the netdev portion before creating a shared branch. Would you be able to review the series?
I think the usual process would be to submit a pull request to both
trees.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: "Nikolova, Tatyana E" <tatyana.e.nikolova@intel.com>
Cc: "jgg@nvidia.com" <jgg@nvidia.com>,
"leon@kernel.org" <leon@kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [iwl-next v5 0/5] Refactor to prepare for Intel IPU E2000 (GEN3)
Date: Thu, 24 Apr 2025 14:51:28 -0700 [thread overview]
Message-ID: <20250424145128.60467c51@kernel.org> (raw)
In-Reply-To: <IA1PR11MB7727AF19E37851E3A4964C77CB852@IA1PR11MB7727.namprd11.prod.outlook.com>
On Thu, 24 Apr 2025 15:58:56 +0000 Nikolova, Tatyana E wrote:
> Would you be able to review this updated patch series?
>
> Netdev maintainers,
>
> Based on Leon's previous comment https://lore.kernel.org/all/20250216111800.GV17863@unreal/, he would like to get acks on the netdev portion before creating a shared branch. Would you be able to review the series?
I think the usual process would be to submit a pull request to both
trees.
next prev parent reply other threads:[~2025-04-24 21:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 2:15 [Intel-wired-lan] [iwl-next v5 0/5] Refactor to prepare for Intel IPU E2000 (GEN3) Tatyana Nikolova
2025-04-16 2:15 ` Tatyana Nikolova
2025-04-16 2:15 ` [Intel-wired-lan] [iwl-next v5 1/5] iidc/ice/irdma: Rename IDC header file Tatyana Nikolova
2025-04-16 2:15 ` Tatyana Nikolova
2025-04-16 2:15 ` [Intel-wired-lan] [iwl-next v5 2/5] iidc/ice/irdma: Rename to iidc_* convention Tatyana Nikolova
2025-04-16 2:15 ` Tatyana Nikolova
2025-04-16 2:15 ` [Intel-wired-lan] [iwl-next v5 3/5] iidc/ice/irdma: Break iidc.h into two headers Tatyana Nikolova
2025-04-16 2:15 ` Tatyana Nikolova
2025-04-16 2:15 ` [Intel-wired-lan] [iwl-next v5 4/5] ice: Replace ice specific DSCP mapping num with a kernel define Tatyana Nikolova
2025-04-16 2:15 ` Tatyana Nikolova
2025-04-17 11:21 ` [Intel-wired-lan] " Simon Horman
2025-04-17 11:21 ` Simon Horman
2025-04-16 2:15 ` [Intel-wired-lan] [iwl-next v5 5/5] iidc/ice/irdma: Update IDC to support multiple consumers Tatyana Nikolova
2025-04-16 2:15 ` Tatyana Nikolova
2025-04-17 11:21 ` [Intel-wired-lan] " Simon Horman
2025-04-17 11:21 ` Simon Horman
2025-04-18 17:14 ` [Intel-wired-lan] " Ertman, David M
2025-04-18 17:14 ` Ertman, David M
2025-04-23 16:14 ` Simon Horman
2025-04-24 15:58 ` [Intel-wired-lan] [iwl-next v5 0/5] Refactor to prepare for Intel IPU E2000 (GEN3) Nikolova, Tatyana E
2025-04-24 15:58 ` Nikolova, Tatyana E
2025-04-24 21:51 ` Jakub Kicinski [this message]
2025-04-24 21:51 ` Jakub Kicinski
2025-04-28 20:29 ` [Intel-wired-lan] " Nikolova, Tatyana E
2025-04-28 20:29 ` Nikolova, Tatyana E
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=20250424145128.60467c51@kernel.org \
--to=kuba@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tatyana.e.nikolova@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.