From: Jakub Kicinski <kuba@kernel.org>
To: jianghaoran <jianghaoran@kylinos.cn>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH V2] taprio: Set the value of picos_per_byte before fill sched_entry
Date: Mon, 3 Oct 2022 08:08:17 -0700 [thread overview]
Message-ID: <20221003080817.27dfd103@kernel.org> (raw)
In-Reply-To: <20221001080626.464349-1-jianghaoran@kylinos.cn>
On Sat, 1 Oct 2022 16:06:26 +0800 jianghaoran wrote:
> Fixes: b5b73b26b3ca ("taprio: Fix allowing too small intervals")
Please note that whenever you put a Fixes tag in a patch you should CC
the authors of the commit in question. get_maintainer will point them
out to you (when run on the patch).
next prev parent reply other threads:[~2022-10-03 15:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 6:58 [PATCH] taprio: Set the value of picos_per_byte before fill sched_entry jianghaoran
2022-09-30 2:18 ` Jakub Kicinski
2022-09-30 11:18 ` jianghaoran
2022-09-30 13:46 ` jianghaoran
2022-09-30 13:58 ` test jianghaoran
2022-09-30 14:16 ` [PATCH] taprio: Set the value of picos_per_byte before fill sched_entry jianghaoran
2022-10-01 0:42 ` jianghaoran
2022-10-01 0:44 ` jianghaoran
2022-10-01 0:49 ` jianghaoran
2022-10-01 0:57 ` jianghaoran
2022-10-01 0:59 ` jianghaoran
2022-10-01 1:10 ` jianghaoran
2022-10-01 1:17 ` jianghaoran
2022-10-01 1:23 ` jianghaoran
2022-10-01 7:48 ` [PATCH V2] " jianghaoran
2022-10-01 7:51 ` jianghaoran
2022-10-01 7:51 ` jianghaoran
2022-10-01 7:53 ` jianghaoran
2022-10-01 8:00 ` jianghaoran
2022-10-01 8:06 ` jianghaoran
2022-10-01 11:44 ` Vladimir Oltean
2022-10-03 15:08 ` Jakub Kicinski [this message]
2022-10-01 8:29 ` jianghaoran
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=20221003080817.27dfd103@kernel.org \
--to=kuba@kernel.org \
--cc=jianghaoran@kylinos.cn \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).