From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 4/6] time: hrtimer: use a bullet for the returns bullet list
Date: Thu, 20 Jun 2019 14:02:33 -0600 [thread overview]
Message-ID: <20190620140233.3d7202ee@lwn.net> (raw)
In-Reply-To: <a4cab6020e0475e7a4afc65dc5854756dd1bfbe9.1560883872.git.mchehab+samsung@kernel.org>
On Tue, 18 Jun 2019 15:51:20 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> That gets rid of this warning:
>
> ./kernel/time/hrtimer.c:1119: WARNING: Block quote ends without a blank line; unexpected unindent.
>
> and displays nicely both at the source code and at the produced
> documentation.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> ---
> kernel/time/hrtimer.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
> index edb230aba3d1..49f78453892f 100644
> --- a/kernel/time/hrtimer.c
> +++ b/kernel/time/hrtimer.c
> @@ -1114,9 +1114,10 @@ EXPORT_SYMBOL_GPL(hrtimer_start_range_ns);
> * @timer: hrtimer to stop
> *
> * Returns:
> - * 0 when the timer was not active
> - * 1 when the timer was active
> - * -1 when the timer is currently executing the callback function and
> + *
> + * • 0 when the timer was not active
> + * • 1 when the timer was active
> + * • -1 when the timer is currently executing the callback function and
> * cannot be stopped
So I have taken some grief for letting non-ASCII stuff into the docs
before; I can only imagine that those who object would be even more
unhappy to see it in a C source file. I'm all for fixing the warning, but
I think we shouldn't start introducing exotic characters at this point...
Thanks,
jon
> */
> int hrtimer_try_to_cancel(struct hrtimer *timer)
next prev parent reply other threads:[~2019-06-20 20:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 18:51 [PATCH 1/6] docs: trace: fix a broken label Mauro Carvalho Chehab
2019-06-18 18:51 ` [PATCH 2/6] docs: trace: add a missing blank line Mauro Carvalho Chehab
2019-06-18 18:59 ` Steven Rostedt
2019-06-19 15:08 ` Masami Hiramatsu
2019-06-20 20:07 ` Jonathan Corbet
2019-06-18 18:51 ` [PATCH 3/6] lib: list_sort.c: add a blank line to avoid kernel-doc warnings Mauro Carvalho Chehab
2019-06-20 20:07 ` Jonathan Corbet
2019-06-18 18:51 ` [PATCH 4/6] time: hrtimer: use a bullet for the returns bullet list Mauro Carvalho Chehab
2019-06-20 20:02 ` Jonathan Corbet [this message]
2019-06-20 20:16 ` Mauro Carvalho Chehab
2019-06-23 10:32 ` Thomas Gleixner
2019-06-18 18:51 ` [PATCH 5/6] docs: signal: fix a kernel-doc markup Mauro Carvalho Chehab
2019-06-18 18:51 ` [PATCH 6/6] drivers: base/node.c: fixes a kernel-doc markups Mauro Carvalho Chehab
2019-06-18 18:55 ` [PATCH v2 " Mauro Carvalho Chehab
2019-06-19 15:09 ` [PATCH 1/6] docs: trace: fix a broken label Masami Hiramatsu
2019-06-20 20:06 ` Jonathan Corbet
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=20190620140233.3d7202ee@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=tglx@linutronix.de \
/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).