From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Changbin Du <changbin.du@huawei.com>
Subject: Re: [PATCH] Rework the jobserver open logic
Date: Wed, 14 Jan 2026 20:40:10 +0100 [thread overview]
Message-ID: <20260114204010.0ddc36fd@foz.lan> (raw)
In-Reply-To: <87h5soupog.fsf@trenco.lwn.net>
Em Wed, 14 Jan 2026 09:25:35 -0700
Jonathan Corbet <corbet@lwn.net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
>
> > On all prints, please use file=sys.stderr.
>
> I was thinking, as I wrote all those, that I needed a warn() function,
> but then it slipped my mind.
well, you could logging. As this is called also inside kernel-doc,
this could be a good idea.
>
> >> + 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[5:]
> >
> > Hmm... moving from partition() to startswith might be problematic...
> > are we sure that "fifo:" can't be in the middle of the string?
>
> If we don't get fifo:file then it's something unexpected and it should
> complain. At least with these changes it will actually complain.
>
> > If so, instead of using "5" magic number, I would use len("fifo:")
>
> I guess, though that's just replacing one constant with another; if
> something changes, both have to be tweaked either way.
I meant:
FIFO = "fifo:"
if fds.startswith(FIFO):
path = fds[len(FIFO):]
(or encapsulate it on a function)
>
> Thanks,
>
> jon
Thanks,
Mauro
prev parent reply other threads:[~2026-01-14 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 20:42 [PATCH] Rework the jobserver open logic Jonathan Corbet
2026-01-14 9:20 ` Mauro Carvalho Chehab
2026-01-14 16:25 ` Jonathan Corbet
2026-01-14 19:40 ` 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=20260114204010.0ddc36fd@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=changbin.du@huawei.com \
--cc=corbet@lwn.net \
--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