mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
Cc: jiri@nvidia.com, davem@davemloft.net, kuba@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	vadym.kochan@plvision.eu, andrew@lunn.ch, nikolay@nvidia.com,
	idosch@idosch.org, sfr@canb.auug.org.au, corbet@lwn.net
Subject: Re: [PATCH net-next v3] documentation: networking: devlink: fix prestera.rst formatting that causes build warnings
Date: Thu, 17 Jun 2021 18:30:04 +0000	[thread overview]
Message-ID: <162395460417.29839.15386152111348932740.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210616174607.5385-1-oleksandr.mazur@plvision.eu>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Wed, 16 Jun 2021 20:46:07 +0300 you wrote:
> Fixes: 66826c43e63d ("documentation: networking: devlink: add prestera switched driver Documentation")
> 
> Signed-off-by: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
> ---
> V3:
>  1) use right commit hash in 'Fixes' tag.
> V2:
>  1) add missing 'net-next' tag in the patch subject.
> 
> [...]

Here is the summary with links:
  - [net-next,v3] documentation: networking: devlink: fix prestera.rst formatting that causes build warnings
    https://git.kernel.org/netdev/net-next/c/01f1b6ed2b84

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



      reply	other threads:[~2021-06-17 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 17:46 Oleksandr Mazur
2021-06-17 18:30 ` 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=162395460417.29839.15386152111348932740.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=idosch@idosch.org \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=oleksandr.mazur@plvision.eu \
    --cc=sfr@canb.auug.org.au \
    --cc=vadym.kochan@plvision.eu \
    /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

all inboxes | Powered by JetHome®