From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: netdev@vger.kernel.org
Cc: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
jesus.s.palencia@gmail.com, ilias.apalodimas@linaro.org
Subject: Re: [PATCH net-next v1 1/4] etf: Cancel timer if there are no pending skbs
Date: Mon, 03 Dec 2018 11:19:45 -0800 [thread overview]
Message-ID: <87pnuia04u.fsf@intel.com> (raw)
In-Reply-To: <20181115012635.7272-1-vinicius.gomes@intel.com>
Hi,
Vinicius Costa Gomes <vinicius.gomes@intel.com> writes:
> From: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>
>
> There is no point in firing the qdisc watchdog if there are no future
> skbs pending in the queue and the watchdog had been set previously.
>
> Signed-off-by: Jesus Sanchez-Palencia <jesus.s.palencia@gmail.com>
It seems that I made a mistake when submitting this series.
It should have been proposed to the net tree (instead of net-next) and
should have included a "Fixes" tag.
Is there a way to have this series considered for the net tree at this
point (given that it already landed on net-next)?
Cheers,
prev parent reply other threads:[~2018-12-03 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 1:26 [PATCH net-next v1 1/4] etf: Cancel timer if there are no pending skbs Vinicius Costa Gomes
2018-11-15 1:26 ` [PATCH net-next v1 2/4] etf: Use cached rb_root Vinicius Costa Gomes
2018-11-17 4:40 ` David Miller
2018-11-15 1:26 ` [PATCH net-next v1 3/4] etf: Split timersortedlist_erase() Vinicius Costa Gomes
2018-11-17 4:40 ` David Miller
2018-11-15 1:26 ` [PATCH net-next v1 4/4] etf: Drop all expired packets Vinicius Costa Gomes
2018-11-17 4:40 ` David Miller
2018-11-17 4:39 ` [PATCH net-next v1 1/4] etf: Cancel timer if there are no pending skbs David Miller
2018-12-03 19:19 ` 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=87pnuia04u.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jesus.s.palencia@gmail.com \
--cc=jesus.sanchez-palencia@intel.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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.