From: John Garry <john.g.garry@oracle.com>
To: Jani Nikula <jani.nikula@linux.intel.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 11:08:49 +0100 [thread overview]
Message-ID: <4bec2735-d501-5359-2ac1-ed0d1fca1cd1@oracle.com> (raw)
In-Reply-To: <878rbmixbn.fsf@intel.com>
On 11/07/2023 10:58, Jani Nikula wrote:
>> I didn't notice anything on dri-devel mailing list about this.
> I presume you're using CONFIG_WERROR=y or W=e.
I'm just using whatever vanilla x86_64_defconfig gives.
>
> See [1] and [2]. I'm undecided how we should treat this.
Ok.
Thanks,
John
next prev parent reply other threads:[~2023-07-11 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 8:35 [Intel-gfx] i915 build issue John Garry
2023-07-11 9:58 ` Jani Nikula
2023-07-11 10:08 ` John Garry [this message]
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=4bec2735-d501-5359-2ac1-ed0d1fca1cd1@oracle.com \
--to=john.g.garry@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox