From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Denis V. Lunev" <den@openvz.org>, qemu-devel@nongnu.org
Cc: John Snow <jsnow@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH 1/1] scripts: fix broken error path in modinfo-collect.py
Date: Thu, 4 Dec 2025 09:37:16 +0100 [thread overview]
Message-ID: <e0b91a24-70e7-4cf4-b2bb-30b9b3401714@linaro.org> (raw)
In-Reply-To: <20251203220138.159656-1-den@openvz.org>
On 3/12/25 23:01, Denis V. Lunev via wrote:
> sys.stderr.print is dropped long ago and should not be used. Official
> replacement is sys.stderr.write
>
> The problem has been found debugging building on some fancy platform
> derived from Debian.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: John Snow <jsnow@redhat.com>
> CC: Cleber Rosa <crosa@redhat.com>
> ---
> scripts/modinfo-collect.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/modinfo-collect.py b/scripts/modinfo-collect.py
> index 6ebaea989d..db78b16c1f 100644
> --- a/scripts/modinfo-collect.py
> +++ b/scripts/modinfo-collect.py
> @@ -41,7 +41,7 @@ def main(args):
> for obj in args:
> entry = compile_commands.get(obj, None)
> if not entry:
> - sys.stderr.print('modinfo: Could not find object file', obj)
> + sys.stderr.write(f'modinfo: Could not find object file {obj}')
Missing trailing '\n'? Otherwise,
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> sys.exit(1)
> src = entry['file']
> if not src.endswith('.c'):
next prev parent reply other threads:[~2025-12-04 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 22:01 [PATCH 1/1] scripts: fix broken error path in modinfo-collect.py Denis V. Lunev via
2025-12-04 8:37 ` Philippe Mathieu-Daudé [this message]
2025-12-08 23:55 ` Denis V. Lunev
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=e0b91a24-70e7-4cf4-b2bb-30b9b3401714@linaro.org \
--to=philmd@linaro.org \
--cc=crosa@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).