public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: o.rempel@pengutronix.de, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	andrew@lunn.ch, mkubecek@suse.cz, thomas.petazzoni@bootlin.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH ethtool-next v2] ethtool: Add missing clause 33 PSE manual description
Date: Mon, 16 Sep 2024 20:10:31 +0000	[thread overview]
Message-ID: <172651743176.3804981.2392553287465994474.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240911-fix_missing_doc-v2-1-e2eade6886b9@bootlin.com>

Hello:

This patch was applied to ethtool/ethtool.git (master)
by Michal Kubecek <mkubecek@suse.cz>:

On Wed, 11 Sep 2024 14:22:04 +0200 you wrote:
> Add missing descriptions for clause 33 options and return values for
> the show-pse and set-pse commands.
> 
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> ---
> Changes in v2:
> - Rebase on top of ethtool-next
> - Link to v1: https://lore.kernel.org/r/20240520-fix_missing_doc-v1-1-965c7debfc0e@bootlin.com
> 
> [...]

Here is the summary with links:
  - [ethtool-next,v2] ethtool: Add missing clause 33 PSE manual description
    https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?id=feea0011ff04

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



      reply	other threads:[~2024-09-16 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 12:22 [PATCH ethtool-next v2] ethtool: Add missing clause 33 PSE manual description Kory Maincent
2024-09-16 20: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=172651743176.3804981.2392553287465994474.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.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