From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 2/2] media: dvb-core: fix demux.h non-ASCII characters
Date: Wed, 30 Aug 2017 19:17:48 -0300 [thread overview]
Message-ID: <20170830191748.40a16438@vento.lan> (raw)
In-Reply-To: <20170830152430.068b13ce@lwn.net>
Em Wed, 30 Aug 2017 15:24:30 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Mon, 28 Aug 2017 16:10:16 -0700
> Randy Dunlap <rdunlap@infradead.org> wrote:
>
> > Fix non-ASCII charactes in kernel-doc comment to prevent the kernel-doc
> > build warning below.
> >
> > WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno ../drivers/media/dvb-core/demux.h' processing failed with: 'ascii' codec can't decode byte 0xe2 in position 6368: ordinal not in range(128)
>
> I'll leave this one for Mauro to decide on. My inclination would be to
> apply it, though, my previous comments on handling non-ASCII text
> notwithstanding. The weird quotes don't buy us anything here.
Yeah, it doesn't make sense to have this character there.
I'll apply it on my tree. Yet, I'm considering adding an UTF-8
character on a kernel-doc markup.
One DVB parameter is called "Rolloff", and its usual symbol is
the greek letter alpha. There, it would make sense to use a
non-ascII character.
By coincidence, I just wrote such patch earlier today.
Regards,
Mauro
prev parent reply other threads:[~2017-08-30 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 23:10 [PATCH 2/2] media: dvb-core: fix demux.h non-ASCII characters Randy Dunlap
2017-08-30 21:24 ` Jonathan Corbet
2017-08-30 22:17 ` Mauro Carvalho Chehab [this message]
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=20170830191748.40a16438@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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.