public inbox for netdev@vger.kernel.org 
 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, edumazet@google•com,
	pabeni@redhat•com, jiri@resnulli•us, linux-doc@vger•kernel.org
Subject: Re: [PATCH net-next v2] docs: netlink: clean up after deprecating version
Date: Wed, 18 Oct 2023 01:10:22 +0000	[thread overview]
Message-ID: <169759142265.24973.8584317282955936096.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231016214540.1822392-1-kuba@kernel.org>

Hello:

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

On Mon, 16 Oct 2023 14:45:40 -0700 you wrote:
> Jiri moved version to legacy specs in commit 0f07415ebb78 ("netlink:
> specs: don't allow version to be specified for genetlink").
> Update the documentation.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel•org>
> ---
> v2:
>  - s/Gobals/Globals/
>  - breaking changes are -> compatibility breaking changes are
>    I think it's plural but the omission of "compatibility" made it confusing
>  - not changing the wording to "should never be used", I prefer existing
> v1: https://lore.kernel.org/all/20231012154315.587383-1-kuba@kernel.org/
> 
> [...]

Here is the summary with links:
  - [net-next,v2] docs: netlink: clean up after deprecating version
    https://git.kernel.org/netdev/net-next/c/5294df643ba6

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-10-18  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 21:45 [PATCH net-next v2] docs: netlink: clean up after deprecating version Jakub Kicinski
2023-10-17  6:10 ` Jiri Pirko
2023-10-18  1: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=169759142265.24973.8584317282955936096.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=jiri@resnulli$(echo .)us \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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