From: Daniel Vetter <daniel@ffwll.ch>
To: "Lespiau, Damien" <damien.lespiau@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: fix FDI_RX_CHICKEN register read masking
Date: Mon, 29 Oct 2012 21:27:03 +0100 [thread overview]
Message-ID: <20121029202703.GQ5691@phenom.ffwll.local> (raw)
In-Reply-To: <CAPX-8+-9sdCzPOqO1quw4XL_nY8gT4V2NC1x=g2Vo000os7z-w@mail.gmail.com>
On Mon, Oct 29, 2012 at 05:49:48PM +0000, Lespiau, Damien wrote:
> On Mon, Oct 29, 2012 at 5:26 PM, Jani Nikula <jani.nikula@intel.com> wrote:
> > Mask the value, not the register. Spotted while reading the code.
> >
> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2012-10-29 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 17:26 [PATCH] drm/i915: fix FDI_RX_CHICKEN register read masking Jani Nikula
2012-10-29 17:49 ` Lespiau, Damien
2012-10-29 20:27 ` Daniel Vetter [this message]
2012-10-29 20:52 ` Daniel Vetter
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=20121029202703.GQ5691@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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