From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Oleksandr Mazur <oleksandr.mazur@plvision.eu>
Subject: Re: linux-next: manual merge of the net-next tree with the jc_docs tree
Date: Fri, 18 Jun 2021 11:25:44 -0600 [thread overview]
Message-ID: <871r8zrso7.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210618115533.0b48bf39@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> Documentation/networking/devlink/devlink-trap.rst
>
> between commit:
>
> 8d4a0adc9cab ("docs: networking: devlink: avoid using ReST :doc:`foo` markup")
>
> from the jc_docs tree and commit:
>
> 01f1b6ed2b84 ("documentation: networking: devlink: fix prestera.rst formatting that causes build warnings")
>
> from the net-next tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc Documentation/networking/devlink/devlink-trap.rst
> index efa5f7f42c88,ef8928c355df..000000000000
> --- a/Documentation/networking/devlink/devlink-trap.rst
> +++ b/Documentation/networking/devlink/devlink-trap.rst
> @@@ -495,8 -495,9 +495,9 @@@ help debug packet drops caused by thes
> links to the description of driver-specific traps registered by various device
> drivers:
>
> - * :doc:`netdevsim`
> - * :doc:`mlxsw`
> - * :doc:`prestera`
> + * Documentation/networking/devlink/netdevsim.rst
> + * Documentation/networking/devlink/mlxsw.rst
> ++ * Documentation/networking/devlink/prestera.rst
This is the right fix, thanks. I got that :doc: directive taken out
even if everybody chose to ignore my request to that end...:)
jon
next prev parent reply other threads:[~2021-06-18 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 1:55 linux-next: manual merge of the net-next tree with the jc_docs tree Stephen Rothwell
2021-06-18 17:25 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-06 23:07 Stephen Rothwell
2019-07-25 0:54 Stephen Rothwell
2018-09-18 0:14 Stephen Rothwell
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=871r8zrso7.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleksandr.mazur@plvision.eu \
--cc=sfr@canb.auug.org.au \
/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).