From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/2] fixup! fixup! drm/xe: Introduce a new DRM driver for Intel GPUs
Date: Tue, 12 Dec 2023 11:00:12 +0200 [thread overview]
Message-ID: <871qbryew3.fsf@intel.com> (raw)
In-Reply-To: <3dquhvnxk5xlmyei6374qmxnveshc62mh5vdemx62krqlqpacq@jrvgdlh6qzdc>
On Tue, 12 Dec 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Mon, Dec 11, 2023 at 10:19:06PM -0500, Rodrigo Vivi wrote:
> Since you are removing the only user, you will need a __maybe_unused in
> pvc_desc, otherwise it fails to build with W=1. With that added (and
> removed in the next fixup patch),
The xe Makefile should enable W=1 warnings locally; have they fallen
behind?
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-12-12 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 3:19 [PATCH 1/2] fixup! fixup! drm/xe: Introduce a new DRM driver for Intel GPUs Rodrigo Vivi
2023-12-12 3:19 ` [PATCH 2/2] fixup! drm/xe: Add PVC's PCI device IDs Rodrigo Vivi
2023-12-12 4:31 ` ✓ CI.Patch_applied: success for series starting with [1/2] fixup! fixup! drm/xe: Introduce a new DRM driver for Intel GPUs Patchwork
2023-12-12 4:31 ` ✗ CI.checkpatch: warning " Patchwork
2023-12-12 4:32 ` ✓ CI.KUnit: success " Patchwork
2023-12-12 4:40 ` ✓ CI.Build: " Patchwork
2023-12-12 4:40 ` ✓ CI.Hooks: " Patchwork
2023-12-12 4:41 ` ✓ CI.checksparse: " Patchwork
2023-12-12 5:16 ` ✓ CI.BAT: " Patchwork
2023-12-12 6:18 ` [PATCH 1/2] " Lucas De Marchi
2023-12-12 9:00 ` Jani Nikula [this message]
2023-12-12 14:04 ` Lucas De Marchi
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=871qbryew3.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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 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.