From: Vinicius Costa Gomes <vinicius.gomes@intel•com>
To: netdev@vger•kernel.org
Cc: jesus.sanchez-palencia@intel•com, henrik@austad•us,
richardcochran@gmail•com, jhs@mojatatu•com,
xiyou.wangcong@gmail•com, jiri@resnulli•us,
ilias.apalodimas@linaro•org, simon.fok@baesystems•com
Subject: Re: [PATCH net-next v1 0/1] net/sched: Introduce the taprio scheduler
Date: Mon, 01 Oct 2018 11:12:17 -0700 [thread overview]
Message-ID: <87murxpmda.fsf@intel.com> (raw)
In-Reply-To: <20180929005943.12928-1-vinicius.gomes@intel.com>
Hi,
Just a small correction, one link on the cover letter is wrong.
Vinicius Costa Gomes <vinicius.gomes@intel•com> writes:
[...]
>
>
> [1] https://patchwork.ozlabs.org/cover/938991/
>
> [2] https://patchwork.ozlabs.org/cover/808504/
>
> [3] github doesn't make it clear, but the gist can be cloned like this:
> $ git clone https://gist.github.com/jeez/bd3afeff081ba64a695008dd8215866f taprio-test
>
> [4] https://github.com/vcgomes/linux/tree/taprio-v1
The correct link is:
[4] https://github.com/vcgomes/net-next
>
> [5] https://github.com/vcgomes/iproute2/tree/taprio-v1
>
>
> Vinicius Costa Gomes (1):
> tc: Add support for configuring the taprio scheduler
>
> include/uapi/linux/pkt_sched.h | 46 ++
> net/sched/Kconfig | 11 +
> net/sched/Makefile | 1 +
> net/sched/sch_taprio.c | 962 +++++++++++++++++++++++++++++++++
> 4 files changed, 1020 insertions(+)
> create mode 100644 net/sched/sch_taprio.c
>
> --
> 2.19.0
Cheers,
prev parent reply other threads:[~2018-10-02 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 0:59 [PATCH net-next v1 0/1] net/sched: Introduce the taprio scheduler Vinicius Costa Gomes
2018-09-29 0:59 ` [PATCH net-next v1 1/1] tc: Add support for configuring " Vinicius Costa Gomes
2018-10-04 20:52 ` David Miller
2018-10-01 18:12 ` Vinicius Costa Gomes [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=87murxpmda.fsf@intel.com \
--to=vinicius.gomes@intel$(echo .)com \
--cc=henrik@austad$(echo .)us \
--cc=ilias.apalodimas@linaro$(echo .)org \
--cc=jesus.sanchez-palencia@intel$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=richardcochran@gmail$(echo .)com \
--cc=simon.fok@baesystems$(echo .)com \
--cc=xiyou.wangcong@gmail$(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