From: Christoph Hellwig <hch@lst.de>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: hch@lst.de, chandanbabu@kernel.org, corbet@lwn.net,
david@fromorbit.com, djwong@kernel.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-xfs@vger.kernel.org, mchehab@kernel.org,
sfr@canb.auug.org.au
Subject: Re: linux-next: build warning after merge of the xfs tree
Date: Mon, 26 Feb 2024 11:57:27 +0100 [thread overview]
Message-ID: <20240226105727.GA28770@lst.de> (raw)
In-Reply-To: <22187737-e0ad-4cc4-98fd-5e43ebc5ecee@gmail.com>
On Sat, Feb 24, 2024 at 06:07:28PM +0900, Akira Yokosawa wrote:
> How about teaching kernel-doc unary "*" on param?
That would be great!
>
> Substitution would look like:
>
> (kernel-doc) (RST)
> *@param -> ***param**
>
> Sphinx detects double asterisk, starts strong emphasis, waits for
> another double asterisk to appear, and stops strong emphasis.
> Hence you would get boldface "*param" in pretty printed docs.
>
> Diff below (against docs-next) should add a rule for param_deref
> (only for RST).
I'd love to go with this instead of working around the issue:
Acked-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-02-26 10:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 4:36 linux-next: build warning after merge of the xfs tree Stephen Rothwell
2024-02-23 6:35 ` Christoph Hellwig
2024-02-23 8:55 ` Mauro Carvalho Chehab
2024-02-23 14:06 ` Christoph Hellwig
2024-02-24 9:07 ` Akira Yokosawa
2024-02-26 10:57 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 4:58 Stephen Rothwell
2026-01-13 7:04 ` Christoph Hellwig
[not found] <D20pUU7kdgWfIpAYmLR776cP2sU4_NhTrc4Fasx5DbMewO7J6UW6QX_81athF3DSSPP2tZiEZNid_Rlin4p6lw==@protonmail.internalid>
2025-09-08 8:04 ` Stephen Rothwell
2025-09-16 10:22 ` Carlos Maiolino
[not found] <95VzqAdwXL6uADPxQWGQV9LD2OtK9bUX7if_opYIYTcdIroqe7176LhnAst-sIYFTfU2tgwJknumIwzvYvxyTQ==@protonmail.internalid>
2025-04-22 10:25 ` Stephen Rothwell
2025-04-22 10:46 ` Carlos Maiolino
2025-04-22 11:38 ` Hans Holmberg
2021-06-07 0:48 Stephen Rothwell
2021-06-07 1:15 ` Dave Chinner
2021-02-08 12:44 Stephen Rothwell
2021-01-24 22:55 Stephen Rothwell
2021-01-25 13:26 ` Brian Foster
2021-01-27 3:14 ` Darrick J. Wong
2020-05-08 1:15 Stephen Rothwell
2020-01-16 0:37 Stephen Rothwell
2020-01-15 22:12 Stephen Rothwell
2020-01-24 2:47 ` Stephen Rothwell
2020-01-24 4:17 ` Darrick J. Wong
2017-10-31 22:42 Stephen Rothwell
2017-08-31 0:07 Stephen Rothwell
2017-08-31 10:30 ` Brian Foster
2017-08-31 14:57 ` Darrick J. Wong
2017-08-31 15:22 ` Brian Foster
2017-08-31 15:41 ` Darrick J. Wong
2017-08-31 21:32 ` Dave Chinner
2010-03-04 0:19 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=20240226105727.GA28770@lst.de \
--to=hch@lst.de \
--cc=akiyks@gmail.com \
--cc=chandanbabu@kernel.org \
--cc=corbet@lwn.net \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.