From: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
To: Vadym Kochan <vadym.kochan@plvision.eu>,
Jonathan Corbet <corbet@lwn.net>
Cc: "jiri@nvidia.com" <jiri@nvidia.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"nikolay@nvidia.com" <nikolay@nvidia.com>,
"idosch@idosch.org" <idosch@idosch.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] documentation: networking: devlink: fix prestera.rst formatting that causes build errors
Date: Tue, 15 Jun 2021 14:44:06 +0000 [thread overview]
Message-ID: <AM0P190MB0738E4FB662B2A626137A629E4309@AM0P190MB0738.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20210615142224.GA18219@plvision.eu>
> Oleksandr Mazur <oleksandr.mazur@plvision.eu> writes:
>
> Fixes: a5aee17deb88 ("documentation: networking: devlink: add prestera switched driver Documentation")
>
> Signed-off-by: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
> ---
> Documentation/networking/devlink/devlink-trap.rst | 1 +
> Documentation/networking/devlink/index.rst | 1 +
> Documentation/networking/devlink/prestera.rst | 4 ++--
> 3 files changed, 4 insertions(+), 2 deletions(-)
Sorry, i've missed the 'net-next' tag in the patch subject. Should i re-send the patch with 'net-next' tag?
E.g. form a V2 patch with proper subject/tag: [PATCH net-next v2] documentation: networking: devlink: fix prestera.rst formatting that causes build errors?
prev parent reply other threads:[~2021-06-15 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 13:48 [PATCH] documentation: networking: devlink: fix prestera.rst formatting that causes build errors Oleksandr Mazur
2021-06-15 14:16 ` Jonathan Corbet
2021-06-15 14:22 ` Vadym Kochan
2021-06-15 14:44 ` Oleksandr Mazur [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=AM0P190MB0738E4FB662B2A626137A629E4309@AM0P190MB0738.EURP190.PROD.OUTLOOK.COM \
--to=oleksandr.mazur@plvision.eu \
--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-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).