From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Vinod Govindapillai <vinod.govindapillai@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2 2/2] drm/i915: disable fbc due to Wa_16023588340
Date: Tue, 02 Jul 2024 13:26:46 +0300 [thread overview]
Message-ID: <871q4c9jix.fsf@intel.com> (raw)
In-Reply-To: <e6d5863b-92fa-468f-bb39-2549eadbb13a@intel.com>
On Tue, 02 Jul 2024, Matthew Auld <matthew.auld@intel.com> wrote:
> So no major objections with going back to v1 from your side? In
> addition, merging both patches via drm-xe-next would be acceptable?
As discussed, and FYI to others, no objections on v1 from me, and ack on
merging via drm-xe-next.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-07-02 10:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 13:27 [PATCH v2 1/2] drm/xe/bmg: implement Wa_16023588340 Matthew Auld
2024-07-01 13:27 ` [PATCH v2 2/2] drm/i915: disable fbc due to Wa_16023588340 Matthew Auld
2024-07-01 16:05 ` Lucas De Marchi
2024-07-02 8:17 ` Jani Nikula
2024-07-02 8:31 ` Matthew Auld
2024-07-02 9:26 ` Jani Nikula
2024-07-02 9:35 ` Matthew Auld
2024-07-02 10:26 ` Jani Nikula [this message]
2024-07-01 17:27 ` ✓ CI.Patch_applied: success for series starting with [v2,1/2] drm/xe/bmg: implement Wa_16023588340 Patchwork
2024-07-01 17:27 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-01 17:28 ` ✓ CI.KUnit: success " Patchwork
2024-07-01 17:40 ` ✓ CI.Build: " Patchwork
2024-07-01 17:42 ` ✓ CI.Hooks: " Patchwork
2024-07-01 17:43 ` ✗ CI.checksparse: warning " Patchwork
2024-07-01 18:06 ` ✓ CI.BAT: success " Patchwork
2024-07-01 19:19 ` ✗ CI.FULL: failure " Patchwork
2024-07-02 7:43 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-07-02 7:43 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-07-02 7:49 ` ✓ Fi.CI.BAT: success " Patchwork
2024-07-02 20:07 ` ✓ 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=871q4c9jix.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=vinod.govindapillai@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.