All of lore.kernel.org
 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, andrew@lunn.ch,
	f.fainelli@gmail.com, mkubecek@suse.cz
Subject: Re: [PATCH net 0/3] ethtool: kdoc fixes
Date: Wed, 07 Apr 2021 22:00:10 +0000	[thread overview]
Message-ID: <161783281026.1764.18302349649104283968.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210407002827.1861191-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Tue,  6 Apr 2021 17:28:24 -0700 you wrote:
> Number of kdoc fixes to ethtool headers. All comment changes.
> 
> With all the patches posted kdoc script seems happy:
> $ ./scripts/kernel-doc -none include/uapi/linux/ethtool.h include/linux/ethtool.h
> $
> 
> Note that some of the changes are in -next, e.g. the FEC
> documentation update so full effect will be seen after
> trees converge.
> 
> [...]

Here is the summary with links:
  - [net,1/3] ethtool: un-kdocify extended link state
    https://git.kernel.org/netdev/net/c/f0ebc2b6b7df
  - [net,2/3] ethtool: document reserved fields in the uAPI
    https://git.kernel.org/netdev/net/c/83e5feeb385e
  - [net,3/3] ethtool: fix kdoc in headers
    https://git.kernel.org/netdev/net/c/d9c65de0c1e1

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



      parent reply	other threads:[~2021-04-07 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  0:28 [PATCH net 0/3] ethtool: kdoc fixes Jakub Kicinski
2021-04-07  0:28 ` [PATCH net 1/3] ethtool: un-kdocify extended link state Jakub Kicinski
2021-04-07  0:28 ` [PATCH net 2/3] ethtool: document reserved fields in the uAPI Jakub Kicinski
2021-04-07  0:28 ` [PATCH net 3/3] ethtool: fix kdoc in headers Jakub Kicinski
2021-04-07 22: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=161783281026.1764.18302349649104283968.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.