From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
linux-kernel@vger.kernel.org, intel-xe@lists.freedesktop.org
Subject: Re: [BUG] allmodconfig build error in next-20240108
Date: Wed, 10 Jan 2024 16:03:51 +1100 [thread overview]
Message-ID: <20240110160335.2bad7d54@oak> (raw)
In-Reply-To: <3d14049c-d44c-4b33-9933-0f96055b8a70@paulmck-laptop>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Hi Paul,
On Tue, 9 Jan 2024 19:46:27 -0800 "Paul E. McKenney" <paulmck@kernel.org> wrote:
>
> On Wed, Jan 10, 2024 at 09:58:22AM +1100, Stephen Rothwell wrote:
> >
> > Maybe that line "subdir-ccflags-y += $(call cc-option, -Wstringop-overflow)"
> > should just be removed as the setting of that option has been moved to the
> > normal C flags in the top level Makefile (out of Makefile.extrawarn).
>
> If you meant like this, no joy. :-(
Actually I meant the one in drivers/gpu/drm/xe/Makefile
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-10 5:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 21:33 [BUG] allmodconfig build error in next-20240108 Paul E. McKenney
2024-01-08 22:57 ` Stephen Rothwell
2024-01-08 23:15 ` Paul E. McKenney
2024-01-09 16:58 ` Lucas De Marchi
2024-01-09 21:11 ` Stephen Rothwell
2024-01-09 22:45 ` Paul E. McKenney
2024-01-09 22:58 ` Stephen Rothwell
2024-01-10 1:09 ` Lucas De Marchi
2024-01-10 3:46 ` Paul E. McKenney
2024-01-10 5:03 ` Stephen Rothwell [this message]
2024-01-10 10:26 ` Paul E. McKenney
2024-01-10 15:00 ` Lucas De Marchi
2024-01-10 15:18 ` Jani Nikula
2024-01-10 15:21 ` Lucas De Marchi
2024-01-10 16:00 ` Paul E. McKenney
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=20240110160335.2bad7d54@oak \
--to=sfr@canb.auug.org.au \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=paulmck@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