From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH RESEND 0/5] drm/i915/opregion updates
Date: Wed, 25 Feb 2015 14:51:15 +0200 [thread overview]
Message-ID: <cover.1424868571.git.jani.nikula@intel.com> (raw)
This has fallen between the cracks. No changes since [1]. The cover letter
copy-pasted from there:
Hi all, here's a few updates to opregion. Patches 1-4 should be pretty
trivial and not do anything drastic. Patch 5 starts using the extended
DIDL, but I doubt it will make a huge difference anyway. It might prove
to be useful prep stuff for adding more sense to our CADL handling.
BR,
Jani.
[1] http://mid.gmane.org/cover.1418303498.git.jani.nikula@intel.com
Jani Nikula (5):
drm/i915/opregion: use BUILD_BUG_ON to verify mailbox struct sizes
drm/i915/opregion: add new opregion stuff
drm/i915/opregion: prefer DRM logging functions over pr_warn and
dev_dbg
drm/i915/opregion: abstract didl and did2 getter and setter
drm/i915/opregion: start using extended didl
drivers/gpu/drm/i915/intel_opregion.c | 104 +++++++++++++++++++++++++---------
1 file changed, 78 insertions(+), 26 deletions(-)
--
2.1.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-02-25 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 12:51 Jani Nikula [this message]
2015-02-25 12:51 ` [PATCH RESEND 1/5] drm/i915/opregion: use BUILD_BUG_ON to verify mailbox struct sizes Jani Nikula
2015-02-25 12:51 ` [PATCH RESEND 2/5] drm/i915/opregion: add new opregion stuff Jani Nikula
2015-02-25 12:51 ` [PATCH RESEND 3/5] drm/i915/opregion: prefer DRM logging functions over pr_warn and dev_dbg Jani Nikula
2015-02-25 12:51 ` [PATCH RESEND 4/5] drm/i915/opregion: abstract didl and did2 getter and setter Jani Nikula
2015-02-25 12:51 ` [PATCH RESEND 5/5] drm/i915/opregion: start using extended didl Jani Nikula
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=cover.1424868571.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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