From: Jonathan Corbet <corbet@lwn.net>
To: duchangbin <changbin.du@huawei.com>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
duchangbin <changbin.du@huawei.com>
Subject: Re: [PATCH v2] Rework the jobserver open logic
Date: Fri, 16 Jan 2026 10:34:12 -0700 [thread overview]
Message-ID: <87bjitpiln.fsf@trenco.lwn.net> (raw)
In-Reply-To: <a295bc17877e417b913b27e7bec8ebd6@huawei.com>
duchangbin <changbin.du@huawei.com> writes:
>> +def warn(text):
>> + print(text, file = sys.stderr)
> Maybe this could be:
> print(f"WARNING: {text}", file = sys.stderr)
> to unify the warnning messages.
Yes, that makes sense.
>> + split_opt = opts[-1].split('=', 1)
>> + if len(split_opt) != 2:
>> + warn('WARNING: unparseable option:', opts[-1])
> Calling the warn() function with two positional arguments, but the function is
> defined to accept only one.
So that is embarrassing. As penance I have now actually tested the
warning paths...
>> + return
>> + fds = split_opt[1]
>> + #
>> + # As of GNU Make 4.4, we'll be looking for a named pipe
>> + # identified as fifo:path
>> + #
>> + if fds.startswith('fifo:'):
>> + path = fds[len('fifo:':]
> Missing a parenthesis.
> path = fds[len('fifo:'):]
...and that is even moreso. I *did* test this before committing it, but
that obviously could never have gotten past the parsing phase. I have
no idea what happened here.
Thanks for taking a look, new version coming shortly.
jon
prev parent reply other threads:[~2026-01-16 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 16:34 [PATCH v2] Rework the jobserver open logic Jonathan Corbet
2026-01-14 20:28 ` Mauro Carvalho Chehab
2026-01-15 2:44 ` duchangbin
2026-01-16 17:34 ` Jonathan Corbet [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=87bjitpiln.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=changbin.du@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox