Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] Revert "drm/i915: use localized __diag_ignore_all() instead of per file"
Date: Tue, 11 Jul 2023 16:10:35 +0100	[thread overview]
Message-ID: <c8b9b49f-0eae-c6f8-0d0d-b2828f1251cc@oracle.com> (raw)
In-Reply-To: <20230711110214.25093-1-jani.nikula@intel.com>

On 11/07/2023 12:02, Jani Nikula wrote:
> This reverts commit 88e9664434c994e97a9f6f8cdd1535495c660cea.
> 
> __diag_ignore_all() only works for GCC 8 or later.
> 
> -Woverride-init (from -Wextra, enabled in i915 Makefile) combined with
> CONFIG_WERROR=y or W=e breaks the build for older GCC.
> 
> With i386_defconfig and x86_64_defconfig enabling CONFIG_WERROR=y by
> default, we really need to roll back the change.
> 
> An alternative would be to disable -Woverride-init in the Makefile for
> GCC <8, but the revert seems like the safest bet now.
> 
> Closes:https://urldefense.com/v3/__https://gitlab.freedesktop.org/drm/intel/-/issues/8768__;!!ACWV5N9M2RV99hQ!IHKvxwtPYBXBj_pfrXmPg5H_6OVsPZaDRDgUUuYsj2IY_JpxM3APirbZR_0yg5UO61Gf2d79Ud7fgySHuVwhOPo$  
> Reported-by: John Garry<john.g.garry@oracle.com>
> References:https://urldefense.com/v3/__https://lore.kernel.org/r/ad2601c0-84bb-c574-3702-a83ff8faf98c@oracle.com__;!!ACWV5N9M2RV99hQ!IHKvxwtPYBXBj_pfrXmPg5H_6OVsPZaDRDgUUuYsj2IY_JpxM3APirbZR_0yg5UO61Gf2d79Ud7fgySH0A7kxf4$  
> References:https://urldefense.com/v3/__https://lore.kernel.org/r/87wmzezns4.fsf@intel.com__;!!ACWV5N9M2RV99hQ!IHKvxwtPYBXBj_pfrXmPg5H_6OVsPZaDRDgUUuYsj2IY_JpxM3APirbZR_0yg5UO61Gf2d79Ud7fgySHAwJkTDk$  
> Fixes: 88e9664434c9 ("drm/i915: use localized __diag_ignore_all() instead of per file")
> Cc: Gustavo Sousa<gustavo.sousa@intel.com>
> Cc: Joonas Lahtinen<joonas.lahtinen@linux.intel.com>
> Cc: Rodrigo Vivi<rodrigo.vivi@intel.com>
> Cc: Tvrtko Ursulin<tvrtko.ursulin@linux.intel.com>
> Signed-off-by: Jani Nikula<jani.nikula@intel.com>

I tested on next-20230711, as this does not apply to v6.5-rc1 (where I 
originally experienced the issue):

Tested-by: John Garry <john.g.garry@oracle.com>

cheers

  parent reply	other threads:[~2023-07-11 15:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 11:02 [Intel-gfx] [PATCH] Revert "drm/i915: use localized __diag_ignore_all() instead of per file" Jani Nikula
2023-07-11 12:02 ` Gustavo Sousa
2023-07-13 16:40   ` Jani Nikula
2023-07-11 15:10 ` John Garry [this message]
2023-07-11 15:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-07-11 15:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-07-11 15:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-11 20:19 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=c8b9b49f-0eae-c6f8-0d0d-b2828f1251cc@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=rodrigo.vivi@intel.com \
    /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