From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: "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: Wed, 30 Aug 2017 16:15:56 -0700 [thread overview]
Message-ID: <4b6e5d98-3030-faa0-bb2d-e8cf3befedbc@infradead.org> (raw)
In-Reply-To: <9bbf28b9-73be-04a2-fa7b-0c3a56ed03bb@infradead.org>
On 08/30/17 16:04, Randy Dunlap wrote:
> On 08/30/17 16:01, Randy Dunlap wrote:
>> On 08/30/17 15:31, Jonathan Corbet wrote:
>>> On Wed, 30 Aug 2017 19:15:53 -0300
>>> Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
>>>
>>>> I suspect that the problem is not related to the version, but to
>>>> what you might have set on LANG.
>>>>
>>>> Maybe if we add something like:
>>>> LANG=C.utf-8
>>>>
>>>> to the Documentation/Makefile
>>>
>>> That's worth a try; Randy, can you give it a quick go?
>>
>> Yes, that fixes it for me. Thanks.
>
> Wait! I forgot to unpatch demux.h. I'll test again now....
OK, still works for me.
>
>>>> or adding:
>>>>
>>>> .. -*- coding: utf-8; mode: rst -*-
>>>>
>>>> as the first line on the *.rst file that include the kernel-doc
>>>> directive would solve the issue.
>>>
>>> I guess I don't see how that would help, instead. Emacs reads that line,
>>> but it's not involved in the problem.
>>>
>>> I wish I could reproduce this, then we could see what in that massive
>>> try..except block in kerneldoc.py is throwing the exception. Putting in
>>> an explicit decode call might be enough to make the problem go away.
>>
>>
>>
>
>
--
~Randy
next prev parent reply other threads:[~2017-08-30 23:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 23:10 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 [this message]
2017-08-31 9:49 ` Mauro Carvalho Chehab
2017-08-31 13:26 ` Jani Nikula
2017-08-31 13:56 ` Mauro Carvalho Chehab
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=4b6e5d98-3030-faa0-bb2d-e8cf3befedbc@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
/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
all inboxes | Powered by JetHome®