From: patchwork-bot+netdevbpf@kernel.org
To: Nguyen@ci.codeaurora.org, Anthony L <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
sasha.neftin@intel.com, vitaly.lifshits@intel.com,
aravindhan.gunasekaran@intel.com
Subject: Re: [PATCH net-next 0/3][pull request] 1GbE Intel Wired LAN Driver Updates 2021-08-27
Date: Sun, 29 Aug 2021 09:50:06 +0000 [thread overview]
Message-ID: <163023060682.19070.7690744992833338059.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210827172513.224045-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 27 Aug 2021 10:25:10 -0700 you wrote:
> Aravindhan Gunasekaran says:
>
> This adds support for Credit-based shaper qdisc offload from
> Traffic Control system. It enables traffic prioritization and
> bandwidth reservation via the Credit-Based Shaper which is
> implemented in hardware by i225 controller.
>
> [...]
Here is the summary with links:
- [net-next,1/3] igc: Use default cycle 'start' and 'end' values for queues
https://git.kernel.org/netdev/net-next/c/c814a2d2d48f
- [net-next,2/3] igc: Simplify TSN flags handling
https://git.kernel.org/netdev/net-next/c/61572d5f8f91
- [net-next,3/3] igc: Add support for CBS offloading
https://git.kernel.org/netdev/net-next/c/1ab011b0bf07
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-08-29 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 17:25 [PATCH net-next 0/3][pull request] 1GbE Intel Wired LAN Driver Updates 2021-08-27 Tony Nguyen
2021-08-27 17:25 ` [PATCH net-next 1/3] igc: Use default cycle 'start' and 'end' values for queues Tony Nguyen
2021-08-27 17:25 ` [PATCH net-next 2/3] igc: Simplify TSN flags handling Tony Nguyen
2021-08-27 17:25 ` [PATCH net-next 3/3] igc: Add support for CBS offloading Tony Nguyen
2021-08-29 9:50 ` patchwork-bot+netdevbpf [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=163023060682.19070.7690744992833338059.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Nguyen@ci.codeaurora.org \
--cc=anthony.l.nguyen@intel.com \
--cc=aravindhan.gunasekaran@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.neftin@intel.com \
--cc=vitaly.lifshits@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.