From: patchwork-bot+netdevbpf@kernel.org
To: Li Zhijian <zhijianx.li@intel.com>
Cc: shuah@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
davem@davemloft.net, peilin.ye@bytedance.com,
cong.wang@bytedance.com, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, philip.li@intel.com,
lizhijian@cn.fujitsu.com, lkp@intel.com
Subject: Re: [PATCH 1/2] selftests/tc-testing: match any qdisc type
Date: Mon, 22 Nov 2021 12:50:09 +0000 [thread overview]
Message-ID: <163758540982.16054.8349984035944815065.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211119062457.16668-1-zhijianx.li@intel.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 19 Nov 2021 14:24:56 +0800 you wrote:
> We should not always presume all kernels use pfifo_fast as the default qdisc.
>
> For example, a fq_codel qdisk could have below output:
> qdisc fq_codel 0: parent 1:4 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
>
> Reported-by: kernel test robot <lkp@intel.com>
> Suggested-by: Peilin Ye <peilin.ye@bytedance.com>
> Signed-off-by: Li Zhijian <zhijianx.li@intel.com>
>
> [...]
Here is the summary with links:
- [1/2] selftests/tc-testing: match any qdisc type
https://git.kernel.org/netdev/net/c/bdf1565fe03d
- [2/2] selftests/tc-testings: Be compatible with newer tc output
https://git.kernel.org/netdev/net/c/ac2944abe4d7
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-11-22 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 6:24 [PATCH 1/2] selftests/tc-testing: match any qdisc type Li Zhijian
2021-11-19 6:24 ` [PATCH 2/2] selftests/tc-testings: Be compatible with newer tc output Li Zhijian
2021-11-22 12: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=163758540982.16054.8349984035944815065.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizhijian@cn.fujitsu.com \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peilin.ye@bytedance.com \
--cc=philip.li@intel.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
--cc=zhijianx.li@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).