From: Jani Nikula <jani.nikula@intel.com>
To: "Swarup\, Aditya" <aditya.swarup@intel.com>, "Roper\,
Matthew D" <matthew.d.roper@intel.com>, "De Marchi\,
Lucas" <lucas.demarchi@intel.com>,
"intel-gfx\@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: [Intel-gfx] topic branch for adl-s: topic/adl-s-enabling
Date: Sat, 16 Jan 2021 11:21:09 +0200 [thread overview]
Message-ID: <87o8hpnsoq.fsf@intel.com> (raw)
I just created a topic branch for adl-s enabling called
topic/adl-s-enabling, based on
git merge-base drm-intel/drm-intel-next drm-intel/drm-intel-gt-next
i.e.
fb5cfcaa2efb ("Merge tag 'drm-intel-gt-next-2021-01-14' of git://anongit.freedesktop.org/drm/drm-intel into drm-next")
The idea is that the adl-s enabling patches get reviewed and applied
here, and when they're all there, it gets merged to both drm-intel-next
and drm-intel-gt-next without delay.
Due to some pressure from Dave Airlie I've had to proceed to apply some
intel_display.c refactoring patches. Let's hope they don't cause too
much trouble.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2021-01-16 9:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87o8hpnsoq.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=aditya.swarup@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@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.