From: patchwork-bot+netdevbpf@kernel.org
To: Kyoji Ogasawara <sawara04.o@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org, netdev@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] smc-sysctl formatting and missing entries
Date: Wed, 11 Mar 2026 01:00:14 +0000 [thread overview]
Message-ID: <177319081454.2986475.15812669905451358310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260309124541.22723-1-sawara04.o@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Mar 2026 21:45:38 +0900 you wrote:
> From: Kyoji Ogasawara <sawara04.o@gmail.com>
>
> Hi,
>
> this series updates SMC sysctl documentation in two small steps.
>
> - patch 1 fixes indentation in the smcr_buf_type section
> - patch 2 documents missing sysctl parameters limit_smc_hs and hs_ctrl,
> including values/defaults and hs_ctrl usage notes
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] net/smc: fix indentation in smcr_buf_type section
https://git.kernel.org/netdev/net-next/c/4a51ac9056c1
- [v2,net-next,2/2] net/smc: Add documentation for limit_smc_hs and hs_ctrl
https://git.kernel.org/netdev/net-next/c/aa5ec9d03b9c
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:[~2026-03-11 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 12:45 [PATCH v2 net-next 0/2] smc-sysctl formatting and missing entries sawara04.o
2026-03-09 12:45 ` [PATCH v2 net-next 1/2] net/smc: fix indentation in smcr_buf_type section sawara04.o
2026-03-09 12:45 ` [PATCH v2 net-next 2/2] net/smc: Add documentation for limit_smc_hs and hs_ctrl sawara04.o
2026-03-10 5:49 ` [PATCH v2 net-next 0/2] smc-sysctl formatting and missing entries D. Wythe
2026-03-11 1: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=177319081454.2986475.15812669905451358310.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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 \
--cc=sawara04.o@gmail.com \
--cc=skhan@linuxfoundation.org \
/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