Linux Documentation
 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, andrew+netdev@lunn.ch, horms@kernel.org,
	corbet@lwn.net, linux-doc@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] docs: net: more adjustments to docs
Date: Fri, 12 Jun 2026 23:20:10 +0000	[thread overview]
Message-ID: <178130641063.1287691.4628986985390612274.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609201224.1191391-1-kuba@kernel.org>

Hello:

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

On Tue,  9 Jun 2026 13:12:21 -0700 you wrote:
> A few small updates to the docs. Mostly typos this time.
> This is trying to prepare docs for getting fed directly
> into AI reviews.
> 
> Jakub Kicinski (3):
>   docs: net: fix minor issues with XDP metadata docs
>   docs: net: tls-offload: document tls_dev_del, tls_dev_resync, and
>     rekey
>   docs: net: fix minor issues with devlink docs
> 
> [...]

Here is the summary with links:
  - [net-next,1/3] docs: net: fix minor issues with XDP metadata docs
    https://git.kernel.org/netdev/net-next/c/6213cf54adad
  - [net-next,2/3] docs: net: tls-offload: document tls_dev_del, tls_dev_resync, and rekey
    (no matching commit)
  - [net-next,3/3] docs: net: fix minor issues with devlink docs
    (no matching commit)

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



      parent reply	other threads:[~2026-06-12 23:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 20:12 [PATCH net-next 0/3] docs: net: more adjustments to docs Jakub Kicinski
2026-06-09 20:12 ` [PATCH net-next 1/3] docs: net: fix minor issues with XDP metadata docs Jakub Kicinski
2026-06-10 23:42   ` Stanislav Fomichev
2026-06-11 10:06   ` Jesper Dangaard Brouer
2026-06-09 20:12 ` [PATCH net-next 2/3] docs: net: tls-offload: document tls_dev_del, tls_dev_resync, and rekey Jakub Kicinski
2026-06-10 21:06   ` Sabrina Dubroca
2026-06-11 17:18     ` Jakub Kicinski
2026-06-11 17:55       ` Sabrina Dubroca
2026-06-11 18:13       ` Randy Dunlap
2026-06-09 20:12 ` [PATCH net-next 3/3] docs: net: fix minor issues with devlink docs Jakub Kicinski
2026-06-12 23:20 ` 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=178130641063.1287691.4628986985390612274.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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