From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch, jgg@ziepe.ca,
leon@kernel.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, david.m.ertman@intel.com,
tatyana.e.nikolova@intel.com, przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next,rdma-next v2 1/5] iidc/ice/irdma: Rename IDC header file
Date: Tue, 13 May 2025 02:20:38 +0000 [thread overview]
Message-ID: <174710283849.1148099.11671684905830521702.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250509200712.2911060-2-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Fri, 9 May 2025 13:07:07 -0700 you wrote:
> From: Dave Ertman <david.m.ertman@intel.com>
>
> To prepare for the IDC upgrade to support different CORE
> PCI drivers, rename header file from iidc.h to iidc_rdma.h
> since this files functionality is specifically for RDMA support.
>
> Use net/dscp.h include in irdma osdep.h and DSCP_MAX type.h,
> instead of iidc header and define.
>
> [...]
Here is the summary with links:
- [net-next,rdma-next,v2,1/5] iidc/ice/irdma: Rename IDC header file
https://git.kernel.org/netdev/net-next/c/468d8b462ac6
- [net-next,rdma-next,v2,2/5] iidc/ice/irdma: Rename to iidc_* convention
https://git.kernel.org/netdev/net-next/c/97b5631aae68
- [net-next,rdma-next,v2,3/5] iidc/ice/irdma: Break iidc.h into two headers
https://git.kernel.org/netdev/net-next/c/d9251a560ba6
- [net-next,rdma-next,v2,4/5] ice: Replace ice specific DSCP mapping num with a kernel define
https://git.kernel.org/netdev/net-next/c/8239b771b94b
- [net-next,rdma-next,v2,5/5] iidc/ice/irdma: Update IDC to support multiple consumers
https://git.kernel.org/netdev/net-next/c/c24a65b6a27c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-05-13 2:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 20:07 [PATCH net-next,rdma-next v2 0/5][pull request] Prepare for Intel IPU E2000 (GEN3) Tony Nguyen
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 1/5] iidc/ice/irdma: Rename IDC header file Tony Nguyen
2025-05-13 2:20 ` patchwork-bot+netdevbpf [this message]
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 2/5] iidc/ice/irdma: Rename to iidc_* convention Tony Nguyen
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 3/5] iidc/ice/irdma: Break iidc.h into two headers Tony Nguyen
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 4/5] ice: Replace ice specific DSCP mapping num with a kernel define Tony Nguyen
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 5/5] iidc/ice/irdma: Update IDC to support multiple consumers Tony Nguyen
2025-05-12 11:05 ` [PATCH net-next,rdma-next v2 0/5][pull request] Prepare for Intel IPU E2000 (GEN3) Leon Romanovsky
2025-05-13 11:21 ` Leon Romanovsky
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=174710283849.1148099.11671684905830521702.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--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 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).