From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Borislav Petkov" <bp@alien8.de>,
x86@kernel.org, "Andy Lutomirski" <luto@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/entry/vdso: fix path to gettimeofday.c
Date: Mon, 9 Mar 2026 20:38:03 +0200 [thread overview]
Message-ID: <20260309183803.efhaoqaxedhrk2bm@skbuf> (raw)
In-Reply-To: <5ed19093-8cf5-4ad5-86e6-457111a7fdd1@zytor.com>
On Sat, Mar 07, 2026 at 04:29:47PM -0800, H. Peter Anvin wrote:
> On 2026-03-07 16:21, Vladimir Oltean wrote:
> >
> > cc="ccache gcc"
> > output_dir=build_allmodconfig_warn/
> > ncpu=$(grep -c processor /proc/cpuinfo)
> > build_flags="-Oline -j $ncpu W=1 C=1"
> > tmpfile_o=$(mktemp)
> > tmpfile_n=$(mktemp)
> >
> > make CC="$cc" O=$output_dir allmodconfig
> > ./scripts/config --file $output_dir/.config -d werror
> > ./scripts/config --file $output_dir/.config -d drm_werror
> > ./scripts/config --file $output_dir/.config -d kvm_werror
> > ./scripts/config --file $output_dir/.config -d rust
> > ./scripts/config --file $output_dir/.config -d security_apparmor
> >
> > make CC="$cc" O=$output_dir $build_flags
>
> Any chance you have a stale ccache?
>
> -hpa
I'm not sure stale in which sense (I don't seem to have problems
otherwise), but I don't really have time to split hairs on such an
insignificant topic, sorry. The include path is wrong.
next prev parent reply other threads:[~2026-03-09 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 17:44 [PATCH] x86/entry/vdso: fix path to gettimeofday.c vladimir.oltean
2026-03-07 19:09 ` Borislav Petkov
2026-03-08 0:21 ` Vladimir Oltean
2026-03-08 0:29 ` H. Peter Anvin
2026-03-09 18:38 ` Vladimir Oltean [this message]
2026-03-09 18:46 ` Borislav Petkov
2026-03-09 19:21 ` Vladimir Oltean
2026-03-10 17:23 ` H. Peter Anvin
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=20260309183803.efhaoqaxedhrk2bm@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--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