From: Damien Lespiau <damien.lespiau@intel.com>
To: Mika Kahola <mika.kahola@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 0/8] All sort of cdclk stuff
Date: Tue, 2 Jun 2015 11:57:33 +0100 [thread overview]
Message-ID: <20150602105733.GA7689@strange.amr.corp.intel.com> (raw)
In-Reply-To: <1433229666-3152-1-git-send-email-mika.kahola@intel.com>
On Tue, Jun 02, 2015 at 10:20:58AM +0300, Mika Kahola wrote:
> This patch series rebases Ville's original cdclk patch series
> excluding the ones that has already been reviewed.
FYI, When a patch that has been reviewed is resent, we usually but the
r-b tags tags along (yes, I know, confusing with what has been said
before)
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-06-02 10:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 7:20 [PATCH v5 0/8] All sort of cdclk stuff Mika Kahola
2015-06-02 7:20 ` [PATCH v5 1/8] drm/i915: Cache current cdclk frequency in dev_priv Mika Kahola
2015-06-02 15:17 ` Jani Nikula
2015-06-03 6:57 ` Mika Kahola
2015-06-02 7:21 ` [PATCH v5 2/8] drm/i915: Use cached cdclk value Mika Kahola
2015-06-02 7:21 ` [PATCH v5 3/8] drm/i915: Unify ilk and hsw .get_aux_clock_divider Mika Kahola
2015-06-02 7:21 ` [PATCH v5 4/8] drm/i915: Store max cdclk value in dev_priv Mika Kahola
2015-06-02 7:21 ` [PATCH v5 5/8] drm/i915: Don't enable IPS when pixel rate exceeds 95% Mika Kahola
2015-06-02 7:21 ` [PATCH v5 6/8] drm/i915: Add IS_BDW_ULX Mika Kahola
2015-06-02 7:21 ` [PATCH v5 7/8] drm/i915: BDW clock change support Mika Kahola
2015-06-02 7:21 ` [PATCH v5 8/8] drm/i915: HSW cdclk support Mika Kahola
2015-06-02 10:46 ` shuang.he
2015-06-02 10:57 ` Damien Lespiau [this message]
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=20150602105733.GA7689@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kahola@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