From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: remove unused mem_block struct definition
Date: Mon, 22 Oct 2012 19:39:40 +0200 [thread overview]
Message-ID: <20121022173940.GH24005@phenom.ffwll.local> (raw)
In-Reply-To: <eeac1e$4ni4db@AZSMGA002.ch.intel.com>
On Mon, Oct 22, 2012 at 02:48:59PM +0100, Chris Wilson wrote:
> On Mon, 22 Oct 2012 16:10:30 +0300, Mika Kuoppala <mika.kuoppala@linux.intel.com> wrote:
> > Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> First you clean up the unused code, then the unwanted and then the
> dysfunctional. And then there will be nothing left!
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2012-10-22 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 13:10 [PATCH] drm/i915: remove unused mem_block struct definition Mika Kuoppala
2012-10-22 13:48 ` Chris Wilson
2012-10-22 17:39 ` Daniel Vetter [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=20121022173940.GH24005@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--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