From: patchwork-bot+netdevbpf@kernel.org
To: Yanteng Si <siyanteng01@gmail.com>
Cc: akiyks@gmail.com, linux@armlinux.org.uk, siyanteng@loongson.cn,
andrew@lunn.ch, corbet@lwn.net, chenhuacai@kernel.org,
hkallweit1@gmail.com, linux-doc@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/2] net: phy: Fix doc build warning
Date: Wed, 08 Dec 2021 05:50:10 +0000 [thread overview]
Message-ID: <163894261084.12550.7172357748660578217.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1638776933.git.siyanteng@loongson.cn>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 6 Dec 2021 16:12:26 +0800 you wrote:
> v2:
>
> * Modified Patch 1/2 under Akira's advices.
>
> * Add Patch 2/2 to fix warning as:
>
> Documentation/networking/kapi:147: ./drivers/net/phy/phylink.c:1657: WARNING: Unexpected indentation.
> Documentation/networking/kapi:147: ./drivers/net/phy/phylink.c:1658: WARNING: Block quote ends without a blank line; unexpected unindent.
>
> [...]
Here is the summary with links:
- [v2,1/2] net: phy: Remove unnecessary indentation in the comments of phy_device
https://git.kernel.org/netdev/net/c/a97770cc4016
- [v2,2/2] net: phy: Add the missing blank line in the phylink_suspend comment
https://git.kernel.org/netdev/net/c/c35e8de70456
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:[~2021-12-08 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 8:12 [PATCH v2 0/2] net: phy: Fix doc build warning Yanteng Si
2021-12-06 8:12 ` [PATCH v2 1/2] net: phy: Remove unnecessary indentation in the comments of phy_device Yanteng Si
2021-12-06 8:12 ` [PATCH v2 2/2] net: phy: Add the missing blank line in the phylink_suspend comment Yanteng Si
2021-12-08 5:50 ` 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=163894261084.12550.7172357748660578217.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyks@gmail.com \
--cc=andrew@lunn.ch \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=hkallweit1@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).