[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221122183850.2cbd942c@gandalf.local.home>
Date: Tue, 22 Nov 2022 18:38:50 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
linux-doc@...r.kernel.org
Subject: Re: [PATCH] Documentation: doc-guide: use '%' constant indicator in
Return: exmaples
On Tue, 22 Nov 2022 10:49:09 -0800
Randy Dunlap <rdunlap@...radead.org> wrote:
> Use the 'constant' indicator '%' in the examples for the
> Return: values syntax. This can help encourage people to use it.
>
Link: https://lore.kernel.org/lkml/20221121154358.36856ca6@gandalf.local.home/
Acked-by: Steven Rostedt (Google) <rostedt@...dmis.org>
-- Steve
> Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
> Suggested-by: Steven Rostedt <rostedt@...dmis.org>
> Cc: Jonathan Corbet <corbet@....net>
> Cc: linux-doc@...r.kernel.org
> ---
> Documentation/doc-guide/kernel-doc.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff -- a/Documentation/doc-guide/kernel-doc.rst b/Documentation/doc-guide/kernel-doc.rst
> --- a/Documentation/doc-guide/kernel-doc.rst
> +++ b/Documentation/doc-guide/kernel-doc.rst
> @@ -151,9 +151,9 @@ named ``Return``.
> line breaks, so if you try to format some text nicely, as in::
>
> * Return:
> - * 0 - OK
> - * -EINVAL - invalid argument
> - * -ENOMEM - out of memory
> + * %0 - OK
> + * %-EINVAL - invalid argument
> + * %-ENOMEM - out of memory
>
> this will all run together and produce::
>
> @@ -163,8 +163,8 @@ named ``Return``.
> ReST list, e. g.::
>
> * Return:
> - * * 0 - OK to runtime suspend the device
> - * * -EBUSY - Device should not be runtime suspended
> + * * %0 - OK to runtime suspend the device
> + * * %-EBUSY - Device should not be runtime suspended
>
> #) If the descriptive text you provide has lines that begin with
> some phrase followed by a colon, each of those phrases will be taken
Powered by blists - more mailing lists