From: patchwork-bot+netdevbpf@kernel.org
To: Tan Tee Min <tee.min.tan@linux.intel.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
stephen@networkplumber.org, vladimir.oltean@nxp.com,
vinicius.gomes@intel.com, muhammad.husaini.zulkifli@intel.com
Subject: Re: [PATCH iproute2-next 1/1] taprio: fix wrong for loop condition in add_tc_entries()
Date: Fri, 02 Dec 2022 16:00:17 +0000 [thread overview]
Message-ID: <166999681792.3415.1993317711039558116.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1669962342-2806-1-git-send-email-tee.min.tan@linux.intel.com>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Fri, 2 Dec 2022 14:25:42 +0800 you wrote:
> The for loop in add_tc_entries() mistakenly included the last entry
> index+1. Fix it to correctly loop the max_sdu entry between tc=0 and
> num_max_sdu_entries-1.
>
> Fixes: b10a6509c195 ("taprio: support dumping and setting per-tc max SDU")
> Signed-off-by: Tan Tee Min <tee.min.tan@linux.intel.com>
>
> [...]
Here is the summary with links:
- [iproute2-next,1/1] taprio: fix wrong for loop condition in add_tc_entries()
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=43aa9d9ce7f8
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:[~2022-12-02 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 6:25 [PATCH iproute2-next 1/1] taprio: fix wrong for loop condition in add_tc_entries() Tan Tee Min
2022-12-02 16:00 ` patchwork-bot+netdevbpf [this message]
2022-12-05 17:23 ` Vladimir Oltean
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=166999681792.3415.1993317711039558116.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tee.min.tan@linux.intel.com \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.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.