From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Hellstrom, Thomas" <thomas.hellstrom@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Hogander, Jouni" <jouni.hogander@intel.com>
Cc: Dave Airlie <airlied@redhat.com>,
"ogabbay@kernel.org" <ogabbay@kernel.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/xe/display: Disable aux ccs framebuffers
Date: Tue, 16 Jan 2024 11:01:45 +0200 [thread overview]
Message-ID: <87bk9lslc6.fsf@intel.com> (raw)
In-Reply-To: <363d705ce20d85a749447d63809a7260a5ca7e34.camel@intel.com>
On Mon, 15 Jan 2024, "Hellstrom, Thomas" <thomas.hellstrom@intel.com> wrote:
> I wonder if, moving forward, we should use a topic/display-for-xe
> branch (no force-push) that can be used for display commits that need
> to be in Xe during -next cycles. It could then be merged into xe and
> i915 as needed?
Topic branches have been discouraged lately, but it's really up to the
drm maintainers. Cc: Dave and Sima, thoughts?
It's also an additional point of confusion for committers to apply to a
topic branch. Deciding between drm-xe-next and drm-intel-next can
already go wrong...
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-16 9:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 18:24 [PATCH] drm/xe/display: Disable aux ccs framebuffers Juha-Pekka Heikkila
2024-01-02 19:44 ` Jani Nikula
2024-01-08 22:18 ` Rodrigo Vivi
2024-01-09 20:40 ` Souza, Jose
2024-01-10 20:09 ` Rodrigo Vivi
2024-01-12 12:31 ` Hogander, Jouni
2024-01-12 21:16 ` Rodrigo Vivi
2024-01-15 13:00 ` Jani Nikula
2024-01-15 15:05 ` Hellstrom, Thomas
2024-01-16 9:01 ` Jani Nikula [this message]
2024-01-04 7:53 ` ✗ Fi.CI.CHECKPATCH: warning for drm/xe/display: Disable aux ccs framebuffers (rev2) Patchwork
2024-01-04 7:53 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-01-04 8:06 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-04 9:15 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-09 20:37 ` [PATCH] drm/xe/display: Disable aux ccs framebuffers Souza, Jose
2024-01-23 10:49 ` Jani Nikula
2024-01-23 17:53 ` Juha-Pekka Heikkila
2024-01-23 17:57 ` Jani Nikula
2024-01-23 18:33 ` Juha-Pekka Heikkila
2024-01-23 12:50 ` Ville Syrjälä
2024-01-23 17:49 ` Juha-Pekka Heikkila
-- strict thread matches above, loose matches on Subject: below --
2024-01-02 18:14 Juha-Pekka Heikkila
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=87bk9lslc6.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jouni.hogander@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@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;
as well as URLs for NNTP newsgroup(s).