netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, vinicius.gomes@intel.com,
	jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, weifeng.voon@intel.com, olteanv@gmail.com,
	kurt@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/7] Small tc-taprio improvements
Date: Tue, 20 Sep 2022 21:10:16 +0000	[thread overview]
Message-ID: <166370821616.24931.5990103349727092023.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220915105046.2404072-1-vladimir.oltean@nxp.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 15 Sep 2022 13:50:39 +0300 you wrote:
> This series contains:
> - the proper protected variant of rcu_dereference() of admin and oper
>   schedules for accesses from the slow path
> - a removal of an extra function pointer indirection for
>   qdisc->dequeue() and qdisc->peek()
> - a removal of WARN_ON_ONCE() checks that can never trigger
> - the addition of netlink extack messages to some qdisc->init() failures
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/7] net/sched: taprio: taprio_offload_config_changed() is protected by rtnl_mutex
    https://git.kernel.org/netdev/net-next/c/c8cbe123be6d
  - [v2,net-next,2/7] net/sched: taprio: taprio_dump and taprio_change are protected by rtnl_mutex
    https://git.kernel.org/netdev/net-next/c/18cdd2f0998a
  - [v2,net-next,3/7] net/sched: taprio: use rtnl_dereference for oper and admin sched in taprio_destroy()
    https://git.kernel.org/netdev/net-next/c/9af23657b336
  - [v2,net-next,4/7] net/sched: taprio: remove redundant FULL_OFFLOAD_IS_ENABLED check in taprio_enqueue
    https://git.kernel.org/netdev/net-next/c/fa65edde5e49
  - [v2,net-next,5/7] net/sched: taprio: stop going through private ops for dequeue and peek
    https://git.kernel.org/netdev/net-next/c/25becba6290b
  - [v2,net-next,6/7] net/sched: taprio: add extack messages in taprio_init
    https://git.kernel.org/netdev/net-next/c/026de64d7bc3
  - [v2,net-next,7/7] net/sched: taprio: replace safety precautions with comments
    https://git.kernel.org/netdev/net-next/c/2c08a4f898d0

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



      parent reply	other threads:[~2022-09-20 21:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 10:50 [PATCH v2 net-next 0/7] Small tc-taprio improvements Vladimir Oltean
2022-09-15 10:50 ` [PATCH v2 net-next 1/7] net/sched: taprio: taprio_offload_config_changed() is protected by rtnl_mutex Vladimir Oltean
2022-09-15 10:50 ` [PATCH v2 net-next 2/7] net/sched: taprio: taprio_dump and taprio_change are " Vladimir Oltean
2022-09-15 10:50 ` [PATCH v2 net-next 3/7] net/sched: taprio: use rtnl_dereference for oper and admin sched in taprio_destroy() Vladimir Oltean
2022-09-15 10:50 ` [PATCH v2 net-next 4/7] net/sched: taprio: remove redundant FULL_OFFLOAD_IS_ENABLED check in taprio_enqueue Vladimir Oltean
2022-09-15 10:50 ` [PATCH v2 net-next 5/7] net/sched: taprio: stop going through private ops for dequeue and peek Vladimir Oltean
2022-09-15 10:50 ` [PATCH v2 net-next 6/7] net/sched: taprio: add extack messages in taprio_init Vladimir Oltean
2022-09-15 10:50 ` [PATCH v2 net-next 7/7] net/sched: taprio: replace safety precautions with comments Vladimir Oltean
2022-09-20 21:01   ` Jakub Kicinski
2022-09-21  0:16     ` Vladimir Oltean
2022-09-21  0:26       ` Jakub Kicinski
2022-09-20 21:10 ` 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=166370821616.24931.5990103349727092023.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.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=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vinicius.gomes@intel.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=weifeng.voon@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).