From: Marc Zyngier <maz@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the irqchip tree
Date: Fri, 03 Sep 2021 10:00:31 +0100 [thread overview]
Message-ID: <ee143a532bf2441b36da947b9b2cb57b@kernel.org> (raw)
In-Reply-To: <20210903164723.176c889e@canb.auug.org.au>
Hi Stephen,
On 2021-09-03 07:47, Stephen Rothwell wrote:
> Hi all,
>
> On Fri, 13 Aug 2021 19:44:57 +1000 Stephen Rothwell
> <sfr@canb.auug.org.au> wrote:
>>
>> After merging the irqchip tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> Documentation/core-api/irq/irq-domain.rst:178: WARNING: Inline
>> emphasis start-string without end-string.
>>
>> Introduced by commit
>>
>> 991007ba6cca ("Documentation: Update irq_domain.rst with new lookup
>> APIs")
>
> I am still getting this warning.
Thanks for the reminder. Fix now queued.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2021-09-03 9:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 9:44 linux-next: build warning after merge of the irqchip tree Stephen Rothwell
2021-09-03 6:47 ` Stephen Rothwell
2021-09-03 9:00 ` Marc Zyngier [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 11:01 Stephen Rothwell
2021-07-08 2:18 ` Stephen Rothwell
2021-07-08 8:10 ` Marc Zyngier
2021-07-08 12:50 ` Stephen Rothwell
2021-07-08 16:32 ` Marc Zyngier
2021-07-08 21:41 ` Stephen Rothwell
2021-06-07 23:21 Stephen Rothwell
2021-06-08 7:36 ` Marc Zyngier
2018-12-14 3:44 Stephen Rothwell
2018-12-15 9:16 ` Marc Zyngier
2014-11-27 6:28 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=ee143a532bf2441b36da947b9b2cb57b@kernel.org \
--to=maz@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).