netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Guedes <andre.guedes@intel.com>
To: netdev@vger.kernel.org
Cc: vinicius.gomes@intel.com, xiyou.wangcong@gmail.com
Subject: [PATCH net-next v2 0/5] Taprio qdisc fixes
Date: Tue, 23 Apr 2019 12:44:19 -0700	[thread overview]
Message-ID: <20190423194424.3155-1-andre.guedes@intel.com> (raw)

Hi all,

I'm re-sending this series, now with the "net-next" prefix in the subject.

The only change from the previous version is in patch 3. As suggested by Cong
Wang, it removes the !entry check within should_restart_cycle() since it is
already checked by the caller. As a side effect, that function becomes a dummy
wrapper on list_is_last() so we simply remove it and call list_is_last()
instead.

Best regards,

Andre

Andre Guedes (5):
  net: sched: taprio: Remove pointless variable assigment
  net: sched: taprio: Refactor taprio_get_start_time()
  net: sched: taprio: Remove should_restart_cycle()
  net: sched: taprio: Fix taprio_peek()
  net: sched: taprio: Fix taprio_dequeue()

 net/sched/sch_taprio.c | 56 +++++++++++++++++++++---------------------
 1 file changed, 28 insertions(+), 28 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-04-23 20:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 19:44 Andre Guedes [this message]
2019-04-23 19:44 ` [PATCH net-next v2 1/5] net: sched: taprio: Remove pointless variable assigment Andre Guedes
2019-04-23 19:44 ` [PATCH net-next v2 2/5] net: sched: taprio: Refactor taprio_get_start_time() Andre Guedes
2019-04-23 19:44 ` [PATCH net-next v2 3/5] net: sched: taprio: Remove should_restart_cycle() Andre Guedes
2019-04-23 19:44 ` [PATCH net-next v2 4/5] net: sched: taprio: Fix taprio_peek() Andre Guedes
2019-04-23 19:44 ` [PATCH net-next v2 5/5] net: sched: taprio: Fix taprio_dequeue() Andre Guedes
2019-04-24  2:52 ` [PATCH net-next v2 0/5] Taprio qdisc fixes David Miller

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=20190423194424.3155-1-andre.guedes@intel.com \
    --to=andre.guedes@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=vinicius.gomes@intel.com \
    --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 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).