Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Graunke <kenneth@whitecape.org>
To: Adam Jackson <ajax@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Pull MTRR setup to its own function
Date: Thu, 15 Mar 2012 16:47:57 -0700	[thread overview]
Message-ID: <4F627FAD.2050000@whitecape.org> (raw)
In-Reply-To: <1331738531-10181-1-git-send-email-ajax@redhat.com>

On 03/14/2012 08:22 AM, Adam Jackson wrote:
> No functional change here, just clarifying code flow.
>
> Signed-off-by: Adam Jackson<ajax@redhat.com>

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>

I'm not qualified to review patch 2, though from the little I know it 
sounds like a good idea.

      parent reply	other threads:[~2012-03-15 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 15:22 [PATCH 1/2] drm/i915: Pull MTRR setup to its own function Adam Jackson
2012-03-14 15:22 ` [PATCH 2/2] drm/i915: Don't do MTRR setup if PAT is enabled Adam Jackson
2012-03-18 17:48   ` Daniel Vetter
2012-03-15 23:47 ` Kenneth Graunke [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=4F627FAD.2050000@whitecape.org \
    --to=kenneth@whitecape.org \
    --cc=ajax@redhat.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