From: Dave Airlie <airlied@gmail.com>
To: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: [Intel-gfx] intel display struct refactor
Date: Mon, 6 Sep 2021 15:55:01 +1000 [thread overview]
Message-ID: <CAPM=9tzoNWJtL4QU6A0zf36Bdw=gfOQ6fnhqg=7QbktvZ5Hv+A@mail.gmail.com> (raw)
I posted an intro set of patches to intel-gfx earlier, but I got a bit
OCD and kept going here.
https://cgit.freedesktop.org/~airlied/linux/log/?h=i915-display-struct-refactor
Mainly looking to see if this is interesting enough refactor to get it
landed, I realise it would be quite disruptive. I'd also like to see
if I missed anything really obvious, I wasn't sure whether
vbt/opregion were suitable and I may have left some stuff behind.
Dave.
reply other threads:[~2021-09-06 5:55 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='CAPM=9tzoNWJtL4QU6A0zf36Bdw=gfOQ6fnhqg=7QbktvZ5Hv+A@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=ville.syrjala@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;
as well as URLs for NNTP newsgroup(s).