netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, jiri@resnulli.us,
	atenart@kernel.org, aroulin@cumulusnetworks.com,
	roopa@nvidia.com
Subject: Re: [PATCH net-next v2] net: remove .ndo_change_proto_down
Date: Tue, 23 Nov 2021 12:30:08 +0000	[thread overview]
Message-ID: <163767060855.14930.6658373290474957799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211123012447.841500-1-kuba@kernel.org>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 22 Nov 2021 17:24:47 -0800 you wrote:
> .ndo_change_proto_down was added seemingly to enable out-of-tree
> implementations. Over 2.5yrs later we still have no real users
> upstream. Hardwire the generic implementation for now, we can
> revert once real users materialize. (rocker is a test vehicle,
> not a user.)
> 
> We need to drop the optimization on the sysfs side, because
> unlike ndos priv_flags will be changed at runtime, so we'd
> need READ_ONCE/WRITE_ONCE everywhere..
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: remove .ndo_change_proto_down
    https://git.kernel.org/netdev/net-next/c/2106efda785b

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



      reply	other threads:[~2021-11-23 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23  1:24 [PATCH net-next v2] net: remove .ndo_change_proto_down Jakub Kicinski
2021-11-23 12:30 ` 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=163767060855.14930.6658373290474957799.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aroulin@cumulusnetworks.com \
    --cc=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@nvidia.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).