From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, intel-xe@lists.freedesktop.org
Subject: Re: [BUG] allmodconfig build error in next-20240108
Date: Wed, 10 Jan 2024 17:18:11 +0200 [thread overview]
Message-ID: <87o7dtusi4.fsf@intel.com> (raw)
In-Reply-To: <6r2zjqbs2g3hkt3uhnglwpboalwck5ye34b6gxzmhe4gae77g7@3bzqt4s7i2qb>
On Wed, 10 Jan 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> [ This particular warning is broken on GCC11. In future changes it will
> be moved to the normal C flags in the top level Makefile (out of
> Makefile.extrawarn), but accounting for the compiler support. Just
> remove it out of xe's forced extra warnings for now ]
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> would you mind if I extend it to drivers/gpu/drm/i915/Makefile
> in the same commit or would you prefer a separate one?
I think I'd prefer separate patches for i915 and xe. And just remove the
line instead of subdir-ccflags-$(call gcc-min-version, 120000) as
linux-next handles it properly in the top level Makefile.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-10 15:18 UTC|newest]
Thread overview: 26+ 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 21:33 ` Paul E. McKenney
2024-01-08 22:57 ` Stephen Rothwell
2024-01-08 22:57 ` Stephen Rothwell
2024-01-08 23:15 ` Paul E. McKenney
2024-01-08 23:15 ` Paul E. McKenney
2024-01-09 16:58 ` Lucas De Marchi
2024-01-09 16:58 ` Lucas De Marchi
2024-01-09 21:11 ` Stephen Rothwell
2024-01-09 21:11 ` Stephen Rothwell
2024-01-09 22:45 ` Paul E. McKenney
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 1:09 ` Lucas De Marchi
2024-01-10 3:46 ` Paul E. McKenney
2024-01-10 5:03 ` Stephen Rothwell
2024-01-10 10:26 ` Paul E. McKenney
2024-01-10 15:00 ` Lucas De Marchi
2024-01-10 15:00 ` Lucas De Marchi
2024-01-10 15:18 ` Jani Nikula [this message]
2024-01-10 15:21 ` Lucas De Marchi
2024-01-10 15:21 ` Lucas De Marchi
2024-01-10 16:00 ` Paul E. McKenney
2024-01-10 16:00 ` Paul E. McKenney
2024-01-09 18:08 ` ✗ CI.Patch_applied: failure for " Patchwork
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=87o7dtusi4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.