From: Dan Carpenter <dan.carpenter@linaro.org>
To: Thomas Gleixner <tglx@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
kernel test robot <lkp@intel.com>,
Ian Rogers <irogers@google.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, sparse@chrisli.org, linux-sparse@vger.kernel.org,
Marco Elver <elver@google.com>
Subject: Re: [PATCH] compiler: Use __typeof_unqual__() for __unqual_scalar_typeof()
Date: Wed, 25 Feb 2026 11:15:27 +0300 [thread overview]
Message-ID: <aZ6vn1NrIkv4UXFW@stanley.mountain> (raw)
In-Reply-To: <87ecnp2zh3.ffs@tglx>
On Fri, Jan 16, 2026 at 07:18:16PM +0100, Thomas Gleixner wrote:
> --- a/Makefile
> +++ b/Makefile
> @@ -1178,6 +1178,14 @@ ifdef CONFIG_CC_IS_CLANG
> KBUILD_USERLDFLAGS += --ld-path=$(LD)
> endif
>
> +# Validate the checker is available and functional
> +ifneq ($(KBUILD_CHECKSRC), 0)
> + ifneq ($(shell $(srctree)/scripts/checker-valid.sh $(CHECK)), 1)
> + $(warning C=$(KBUILD_CHECKSRC) specified, but $(CHECK) is not available or not up to date)
> + KBUILD_CHECKSRC = 0
> + endif
> +endif
> +
This means we can't run "CHECK="valgrind smatch -p=kernel" because
valgrind always prints output to stderr. So hopefully we can
eventually remove this check.
regards,
dan carpenter
prev parent reply other threads:[~2026-02-25 8:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202601150001.sKSN644a-lkp@intel.com>
2026-01-15 19:28 ` [tip:timers/vdso 12/14] net/rds/ib_cm.c:96:35: sparse: sparse: incorrect type in argument 1 (different modifiers) Thomas Gleixner
2026-01-15 21:11 ` Peter Zijlstra
2026-01-15 21:19 ` Linus Torvalds
2026-01-15 21:30 ` Peter Zijlstra
2026-01-15 23:03 ` Linus Torvalds
2026-01-16 8:28 ` Peter Zijlstra
2026-01-15 23:01 ` Thomas Gleixner
2026-01-16 11:25 ` Thomas Gleixner
2026-01-16 18:18 ` [PATCH] compiler: Use __typeof_unqual__() for __unqual_scalar_typeof() Thomas Gleixner
2026-01-17 5:25 ` Ian Rogers
2026-02-25 8:15 ` Dan Carpenter [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=aZ6vn1NrIkv4UXFW@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=elver@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=sparse@chrisli.org \
--cc=tglx@kernel.org \
--cc=x86@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