All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: John Garry <john.g.garry@oracle.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
	tvrtko.ursulin@linux.intel.com
Subject: Re: [Intel-gfx] i915 build issue
Date: Tue, 11 Jul 2023 12:58:36 +0300	[thread overview]
Message-ID: <878rbmixbn.fsf@intel.com> (raw)
In-Reply-To: <ad2601c0-84bb-c574-3702-a83ff8faf98c@oracle.com>

On Tue, 11 Jul 2023, John Garry <john.g.garry@oracle.com> wrote:
> Hi guys,
>
> Did anyone else notice this build issue on v6.5-rc1:
>
> drivers/gpu/drm/i915/i915_pci.c:143:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:151:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:159:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:166:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:174:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:180:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:186:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:209:15: error: initialized field
> overwritten [-Werror=override-init]
>    .has_snoop = false,
>                 ^~~~~
> ...
>
> I'm using following gcc:
>
> john@localhost:~/mnt_sda4/john/linux> gcc --version
> gcc (SUSE Linux) 7.5.0
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> I didn't notice anything on dri-devel mailing list about this.

I presume you're using CONFIG_WERROR=y or W=e.

See [1] and [2]. I'm undecided how we should treat this.


BR,
Jani.


[1] https://lore.kernel.org/r/87wmzezns4.fsf@intel.com
[2] https://gitlab.freedesktop.org/drm/intel/-/issues/8768


-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: John Garry <john.g.garry@oracle.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
	tvrtko.ursulin@linux.intel.com
Subject: Re: i915 build issue
Date: Tue, 11 Jul 2023 12:58:36 +0300	[thread overview]
Message-ID: <878rbmixbn.fsf@intel.com> (raw)
In-Reply-To: <ad2601c0-84bb-c574-3702-a83ff8faf98c@oracle.com>

On Tue, 11 Jul 2023, John Garry <john.g.garry@oracle.com> wrote:
> Hi guys,
>
> Did anyone else notice this build issue on v6.5-rc1:
>
> drivers/gpu/drm/i915/i915_pci.c:143:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:151:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:159:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:166:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:174:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:180:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:186:15: error: expected expression
> before ‘,’ token
>    GEN3_FEATURES,
>                 ^
> drivers/gpu/drm/i915/i915_pci.c:209:15: error: initialized field
> overwritten [-Werror=override-init]
>    .has_snoop = false,
>                 ^~~~~
> ...
>
> I'm using following gcc:
>
> john@localhost:~/mnt_sda4/john/linux> gcc --version
> gcc (SUSE Linux) 7.5.0
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> I didn't notice anything on dri-devel mailing list about this.

I presume you're using CONFIG_WERROR=y or W=e.

See [1] and [2]. I'm undecided how we should treat this.


BR,
Jani.


[1] https://lore.kernel.org/r/87wmzezns4.fsf@intel.com
[2] https://gitlab.freedesktop.org/drm/intel/-/issues/8768


-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-07-11  9:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  8:35 [Intel-gfx] i915 build issue John Garry
2023-07-11  8:35 ` John Garry
2023-07-11  9:58 ` Jani Nikula [this message]
2023-07-11  9:58   ` Jani Nikula
2023-07-11 10:08   ` [Intel-gfx] " John Garry
2023-07-11 10:08     ` John Garry
2023-07-11 11:05     ` [Intel-gfx] " Jani Nikula
2023-07-11 11:05       ` Jani Nikula

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=878rbmixbn.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=john.g.garry@oracle.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tvrtko.ursulin@linux.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 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.