From: Chris Wilson <chris@chris-wilson.co.uk>
To: Haixia Shi <hshi@chromium.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/udl: fix excessive prefetch_range
Date: Wed, 28 Jan 2015 20:56:35 +0000 [thread overview]
Message-ID: <20150128205635.GI25850@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1422468930-20592-2-git-send-email-hshi@chromium.org>
On Wed, Jan 28, 2015 at 10:15:30AM -0800, Haixia Shi wrote:
> The prefetch_range amount is already in number of bytes. Multiplying again by
> bpp is unnecessary.
>
> Signed-off-by: Haixia Shi <hshi@chromium.org>
> Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
> Tested-by: Haixia Shi <hshi@chromium.org>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-28 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 18:15 [PATCH 1/2] drm/udl: optimize udl_compress_hline16 Haixia Shi
2015-01-28 18:15 ` [PATCH 2/2] drm/udl: fix excessive prefetch_range Haixia Shi
2015-01-28 20:56 ` Chris Wilson [this message]
2015-01-28 21:12 ` [PATCH 1/2] drm/udl: optimize udl_compress_hline16 Chris Wilson
2015-01-28 21:41 ` Haixia Shi
2015-01-28 21:41 ` [PATCH 2/2] drm/udl: fix excessive prefetch_range Haixia Shi
2015-01-30 3:45 ` [PATCH 1/2] drm/udl: optimize udl_compress_hline16 Dave Airlie
2015-01-30 18:20 ` Haixia Shi
2015-01-30 18:49 ` Haixia Shi
2015-01-30 18:49 ` [PATCH 2/2] drm/udl: fix excessive prefetch_range Haixia Shi
2015-01-30 18:51 ` [PATCH 1/2] drm/udl: optimize udl_compress_hline16 (v2) Haixia Shi
2015-01-30 18:51 ` [PATCH 2/2] drm/udl: fix excessive prefetch_range (v2) Haixia Shi
2015-01-28 21:50 ` [PATCH 1/2] drm/udl: optimize udl_compress_hline16 Haixia Shi
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=20150128205635.GI25850@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=hshi@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.