From: Markus Elfring <Markus.Elfring@web.de>
To: lkp@intel.com, acpica-devel@lists.linux.dev, bpf@vger.kernel.org,
coresight@lists.linaro.org, kvm@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, linux-perf-users@vger.kernel.org,
linux-pm@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, mptcp@lists.linux.dev,
netdev@vger.kernel.org, platform-driver-x86@vger.kernel.org,
virtualization@lists.linux.dev,
Adrian Hunter <adrian.hunter@intel.com>,
Alex Mastro <amastro@fb.com>, Alex Williamson <alex@shazbot.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Alexei Starovoitov <ast@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Andrew Morton <akpm@linux-foundation.org>,
Andrii Nakryiko <andrii@kernel.org>,
Ankur Arora <ankur.a.arora@oracle.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: tools: Use fputc() calls in some functions
Date: Fri, 7 Aug 2026 08:33:08 +0200 [thread overview]
Message-ID: <c27214da-4e76-4b5d-ab86-ab03beba8f6f@web.de> (raw)
In-Reply-To: <202608070547.MRKfa3bH-lkp@intel.com>
…
> All errors (new ones prefixed by >>):
>
>>> builtin-check.c:300:8: error: incompatible pointer to integer conversion passing 'FILE *' (aka 'struct _IO_FILE *') to parameter of type 'int' [-Wint-conversion]
> 300 | fputc(stderr, '\n');
> | ^~~~~~
> /usr/include/stdio.h:155:16: note: expanded from macro 'stderr'
> 155 | #define stderr stderr
> | ^~~~~~
> /usr/include/stdio.h:611:23: note: passing argument to parameter '__c' here
> 611 | extern int fputc (int __c, FILE *__stream) __nonnull ((2));
> | ^…
Would you become interested to take another look at a corrected source code transformation approach?
Improving output for single characters (with SmPL)?
https://lore.kernel.org/cocci/406093f5-ee7d-4ae9-808b-2b42d4846eab@web.de/
https://sympa.inria.fr/sympa/arc/cocci/2026-07/msg00055.html
https://lkml.org/lkml/2026/7/23/2205
Can similar adjustments become more helpful for further software areas?
Regards,
Markus
prev parent reply other threads:[~2026-08-07 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 10:25 [PATCH] tools: Use fputc() calls in some functions Markus Elfring
2026-07-23 13:47 ` Andi Kleen
2026-07-23 14:33 ` Steven Rostedt
2026-07-23 15:14 ` Segher Boessenkool
2026-07-23 15:07 ` bot+bpf-ci
2026-07-23 15:07 ` bot+bpf-ci
2026-07-23 15:07 ` bot+bpf-ci
2026-08-06 17:40 ` kernel test robot
2026-08-06 21:50 ` kernel test robot
2026-08-07 6:33 ` Markus Elfring [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=c27214da-4e76-4b5d-ab86-ab03beba8f6f@web.de \
--to=markus.elfring@web.de \
--cc=acme@kernel.org \
--cc=acpica-devel@lists.linux.dev \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alex@shazbot.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=amastro@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrii@kernel.org \
--cc=ankur.a.arora@oracle.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brgl@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.