From: patchwork-bot+netdevbpf@kernel.org
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, vadim.fedorenko@linux.dev,
arkadiusz.kubalewski@intel.com, jiri@resnulli.us, corbet@lwn.net,
davem@davemloft.net
Subject: Re: [PATCH net-next v2 0/2] Documentation fixes for dpll subsystem
Date: Tue, 03 Oct 2023 22:10:33 +0000 [thread overview]
Message-ID: <169637103325.17710.5593789278603779444.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230928052708.44820-1-bagasdotme@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 28 Sep 2023 12:27:06 +0700 you wrote:
> Here is a mini docs fixes for dpll subsystem. The fixes are all code
> block-related.
>
> This series is triggered because I was emailed by kernel test robot,
> alerting htmldocs warnings (see patch [1/2]).
>
> Changes since v1 [1]:
> * Collect Reviewed-by tags
> * Rebase on current net-next
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] Documentation: dpll: Fix code blocks
https://git.kernel.org/netdev/net-next/c/92425d08a608
- [net-next,v2,2/2] Documentation: dpll: wrap DPLL_CMD_PIN_GET output in a code block
https://git.kernel.org/netdev/net-next/c/c8afdc018329
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:[~2023-10-03 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 5:27 [PATCH net-next v2 0/2] Documentation fixes for dpll subsystem Bagas Sanjaya
2023-09-28 5:27 ` [PATCH net-next v2 1/2] Documentation: dpll: Fix code blocks Bagas Sanjaya
2023-09-28 20:42 ` Randy Dunlap
2023-09-28 5:27 ` [PATCH net-next v2 2/2] Documentation: dpll: wrap DPLL_CMD_PIN_GET output in a code block Bagas Sanjaya
2023-09-28 20:42 ` Randy Dunlap
2023-09-29 1:00 ` [PATCH net-next v2 0/2] Documentation fixes for dpll subsystem Vadim Fedorenko
2023-10-03 22: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=169637103325.17710.5593789278603779444.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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