From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-doc\@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH 1/2] docs: kernel-doc comments are ASCII
Date: Thu, 31 Aug 2017 10:56:26 -0300 [thread overview]
Message-ID: <20170831105602.5607fe52@vento.lan> (raw)
In-Reply-To: <87h8wn98bv.fsf@intel.com>
Em Thu, 31 Aug 2017 16:26:44 +0300
Jani Nikula <jani.nikula@linux.intel.com> escreveu:
> On Thu, 31 Aug 2017, Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> > As Documentation/conf.py has:
> >
> > # -*- coding: utf-8 -*-
> >
> > on its first line, I suspect that the error you're getting is likely
> > due to the usage of a python version that doesn't recognize this.
>
> AFAIK that has nothing to do with python I/O, and everything to do with
> the encoding of that specific python source file.
Jani,
It should have something to do with python version and/or to some
locale info at the system, as neither I or Jon can reproduce it.
Can you reproduce it on your system?
Thanks,
Mauro
next prev parent reply other threads:[~2017-08-31 13:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 23:10 [PATCH 1/2] docs: kernel-doc comments are ASCII Randy Dunlap
2017-08-30 21:23 ` Jonathan Corbet
2017-08-30 22:02 ` Randy Dunlap
2017-08-30 22:15 ` Mauro Carvalho Chehab
2017-08-30 22:31 ` Jonathan Corbet
2017-08-30 23:01 ` Randy Dunlap
2017-08-30 23:04 ` Randy Dunlap
2017-08-30 23:15 ` Randy Dunlap
2017-08-31 9:49 ` Mauro Carvalho Chehab
2017-08-31 13:26 ` Jani Nikula
2017-08-31 13:56 ` Mauro Carvalho Chehab [this message]
2017-08-31 14:17 ` Jonathan Corbet
2017-08-31 15:47 ` Randy Dunlap
2017-08-31 16:05 ` Jani Nikula
2017-08-31 16:24 ` Randy Dunlap
2017-08-31 16:36 ` Jani Nikula
2017-08-31 17:34 ` Randy Dunlap
2017-08-31 17:54 ` Randy Dunlap
2017-08-31 17:55 ` Jani Nikula
2017-08-31 18:08 ` Randy Dunlap
2017-08-31 15:44 ` Randy Dunlap
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=20170831105602.5607fe52@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--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.