All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, jiri@resnulli.us,
	vinicius.gomes@intel.com, kurt@linutronix.de,
	gerhard@engleder-embedded.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] taprio queueMaxSDU fixes
Date: Mon, 20 Feb 2023 08:00:16 +0000	[thread overview]
Message-ID: <167688001647.8258.280190584176814049.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230215224632.2532685-1-vladimir.oltean@nxp.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Thu, 16 Feb 2023 00:46:29 +0200 you wrote:
> This fixes 3 issues noticed while attempting to reoffload the
> dynamically calculated queueMaxSDU values. These are:
> - Dynamic queueMaxSDU is not calculated correctly due to a lost patch
> - Dynamically calculated queueMaxSDU needs to be clamped on the low end
> - Dynamically calculated queueMaxSDU needs to be clamped on the high end
> 
> Vladimir Oltean (3):
>   net/sched: taprio: fix calculation of maximum gate durations
>   net/sched: taprio: don't allow dynamic max_sdu to go negative after
>     stab adjustment
>   net/sched: taprio: dynamic max_sdu larger than the max_mtu is
>     unlimited
> 
> [...]

Here is the summary with links:
  - [net-next,1/3] net/sched: taprio: fix calculation of maximum gate durations
    https://git.kernel.org/netdev/net-next/c/09dbdf28f9f9
  - [net-next,2/3] net/sched: taprio: don't allow dynamic max_sdu to go negative after stab adjustment
    https://git.kernel.org/netdev/net-next/c/bdf366bd867c
  - [net-next,3/3] net/sched: taprio: dynamic max_sdu larger than the max_mtu is unlimited
    https://git.kernel.org/netdev/net-next/c/64cb6aad1232

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-02-20  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 22:46 [PATCH net-next 0/3] taprio queueMaxSDU fixes Vladimir Oltean
2023-02-15 22:46 ` [PATCH net-next 1/3] net/sched: taprio: fix calculation of maximum gate durations Vladimir Oltean
2023-02-16  9:27   ` Kurt Kanzenbach
2023-02-15 22:46 ` [PATCH net-next 2/3] net/sched: taprio: don't allow dynamic max_sdu to go negative after stab adjustment Vladimir Oltean
2023-02-16  9:27   ` Kurt Kanzenbach
2023-02-15 22:46 ` [PATCH net-next 3/3] net/sched: taprio: dynamic max_sdu larger than the max_mtu is unlimited Vladimir Oltean
2023-02-16  9:28   ` Kurt Kanzenbach
2023-02-16 10:29     ` Vladimir Oltean
2023-02-16 10:34       ` Kurt Kanzenbach
2023-02-16 10:35       ` Vladimir Oltean
2023-02-20  8:00 ` 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=167688001647.8258.280190584176814049.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gerhard@engleder-embedded.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=kurt@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vinicius.gomes@intel.com \
    --cc=vladimir.oltean@nxp.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 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.