From: patchwork-bot+netdevbpf@kernel.org
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
netdev@vger.kernel.org, linux-hams@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
krzk@kernel.org, ajk@comnets.uni-bremen.de
Subject: Re: [PATCH net-next 0/2] networking docs section headings cleanup
Date: Tue, 21 Oct 2025 09:00:09 +0000 [thread overview]
Message-ID: <176103720951.983008.17974631563235694861.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251017064525.28836-2-bagasdotme@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 17 Oct 2025 13:45:24 +0700 you wrote:
> Hi,
>
> Just two net docs patches cleaning up section headings. The shortlog below
> should be self-explanatory.
>
> Enjoy!
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: nfc: Format userspace interface subsection headings
https://git.kernel.org/netdev/net-next/c/122d696c1789
- [net-next,2/2] net: 6pack: Demote "How to turn on 6pack support" section heading
https://git.kernel.org/netdev/net-next/c/97aa8ecb5732
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-21 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 6:45 [PATCH net-next 0/2] networking docs section headings cleanup Bagas Sanjaya
2025-10-17 6:45 ` [PATCH net-next 1/2] net: nfc: Format userspace interface subsection headings Bagas Sanjaya
2025-10-17 6:45 ` [PATCH net-next 2/2] net: 6pack: Demote "How to turn on 6pack support" section heading Bagas Sanjaya
2025-10-21 9: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=176103720951.983008.17974631563235694861.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ajk@comnets.uni-bremen.de \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@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