public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Wei Fang <wei.fang@nxp•com>
Cc: claudiu.manoil@nxp•com, vladimir.oltean@nxp•com,
	davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
	pabeni@redhat•com, maciej.fijalkowski@intel•com,
	netdev@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH V2 net] net: enetc: correct the indexes of highest and 2nd highest TCs
Date: Thu, 08 Jun 2023 20:00:20 +0000	[thread overview]
Message-ID: <168625442043.20484.1204424752375765875.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230607091048.1152674-1-wei.fang@nxp.com>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft•net>:

On Wed,  7 Jun 2023 17:10:48 +0800 you wrote:
> From: Wei Fang <wei.fang@nxp•com>
> 
> For ENETC hardware, the TCs are numbered from 0 to N-1, where N
> is the number of TCs. Numerically higher TC has higher priority.
> It's obvious that the highest priority TC index should be N-1 and
> the 2nd highest priority TC index should be N-2.
> 
> [...]

Here is the summary with links:
  - [V2,net] net: enetc: correct the indexes of highest and 2nd highest TCs
    https://git.kernel.org/netdev/net/c/21225873be14

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-06-08 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  9:10 [PATCH V2 net] net: enetc: correct the indexes of highest and 2nd highest TCs wei.fang
2023-06-07 11:07 ` Maciej Fijalkowski
2023-06-08 20:00 ` 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=168625442043.20484.1204424752375765875.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=claudiu.manoil@nxp$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=maciej.fijalkowski@intel$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=vladimir.oltean@nxp$(echo .)com \
    --cc=wei.fang@nxp$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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