From: Jonathan Corbet <corbet@lwn•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Tejun Heo <tj@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the cgroup tree
Date: Fri, 12 Jul 2024 08:48:19 -0600 [thread overview]
Message-ID: <8734oe1xak.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240712165107.7b46a640@canb.auug.org.au>
Stephen Rothwell <sfr@canb•auug.org.au> writes:
> Hi all,
>
> On Fri, 12 Jul 2024 16:43:54 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>>
>> After merging the cgroup tree, today's linux-next build (htmldocs)
>> failed like this:
>>
>> Sphinx parallel build error:
>> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfd in position 558: invalid start byte
>>
>> Caused by commit
>>
>> 704f684e15ad ("cgroup: Add Michal Koutný as a maintainer")
>>
>> I tracked this down using
>>
>> git diff stable.. | cat -v | grep -F 'M-}'
>>
>> and finding the commit that added the line that was output.
>> I tested it by building with the commit temporarily reverted. I have
>> left that commit in today's linux-next.
>>
>> Clearly (I think) there is nothing wrong with the commit, but the Sphinx
>> utf-8 decoder also clearly does not think it is valid UTF-8 :-(
>
> Actually my character map app says that it should be the two bytes 0xC3
> 0xBD in UTF-8 (it is 0x00FD in UTF-16).
As you observed, the patch is encoded in ISO-8859, not UTF8; that
doesn't fit well in a file that uses UTF8. One could argue that Sphinx
should be a bit more robust, but satisfactory results will not be had
regardless.
An encoding check might be a useful thing to have in checkpatch.pl,
methinks.
jon
next prev parent reply other threads:[~2024-07-12 14:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 6:43 linux-next: build failure after merge of the cgroup tree Stephen Rothwell
2024-07-12 6:51 ` Stephen Rothwell
2024-07-12 14:48 ` Jonathan Corbet [this message]
2024-07-12 16:44 ` Tejun Heo
2024-07-12 16:50 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2025-08-25 5:03 Stephen Rothwell
2025-08-25 18:18 ` Tejun Heo
2023-12-07 3:38 Stephen Rothwell
2023-12-07 4:18 ` Waiman Long
2023-07-17 1:34 Stephen Rothwell
2023-07-17 6:45 ` Miaohe Lin
2022-10-31 2:23 Stephen Rothwell
2022-10-31 17:52 ` Tejun Heo
2022-09-12 6:18 Stephen Rothwell
2022-09-12 7:38 ` Peter Zijlstra
2022-09-12 18:44 ` Tejun Heo
2022-09-12 22:16 ` Tejun Heo
2022-09-15 10:46 ` Peter Zijlstra
2022-10-10 20:57 ` Stephen Rothwell
2022-10-10 20:59 ` Tejun Heo
2022-08-29 3:29 Stephen Rothwell
2021-05-11 0:51 Stephen Rothwell
2021-05-11 1:10 ` Roman Gushchin
2021-05-11 1:31 ` Tejun Heo
2021-04-22 6:31 Stephen Rothwell
2015-09-25 3:26 Stephen Rothwell
2014-02-26 6:46 Stephen Rothwell
2014-02-26 13:44 ` Tejun Heo
2013-04-29 4:04 Stephen Rothwell
2013-04-29 22:55 ` Tejun Heo
2013-04-30 1:51 ` Benjamin Herrenschmidt
2012-09-14 3:17 Stephen Rothwell
2012-09-14 6:56 ` Daniel Wagner
2012-09-14 17:00 ` Tejun Heo
2012-09-14 18:32 ` Sedat Dilek
2012-09-14 18:34 ` Tejun Heo
2012-09-15 7:55 ` Sedat Dilek
2011-11-25 3:50 Stephen Rothwell
2011-11-27 19:33 ` Tejun Heo
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=8734oe1xak.fsf@trenco.lwn.net \
--to=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tj@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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