From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove unused workaround bb code and unused struct members
Date: Wed, 10 Jan 2018 14:54:53 +0000 [thread overview]
Message-ID: <c4d73235-b4dd-ee7d-5d63-02da6f95e057@linux.intel.com> (raw)
In-Reply-To: <151558863081.23681.95844224813819260@mail.alporthouse.com>
On 10/01/2018 12:50, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-01-10 12:24:49)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> After recent code changes this part of the code now looks over-engineered
>> and can be simplified, together with the corresponding struct members.
>
> I don't mind, but I was keeping it around just in case we ever need to
> re-instantiate a per-bb wa batch.
>
> If the consensus is we won't need one for the foreseeable future,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
I expected something like that. I don't see anybody using it, but I also
don't mind if the scaffolding stays in. I'll let it hang out there, and
in case someone needs it it's there.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-10 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 12:24 [PATCH] drm/i915: Remove unused workaround bb code and unused struct members Tvrtko Ursulin
2018-01-10 12:43 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-10 12:50 ` [PATCH] " Chris Wilson
2018-01-10 14:54 ` Tvrtko Ursulin [this message]
2018-01-10 14:08 ` ✓ Fi.CI.IGT: success for " Patchwork
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=c4d73235-b4dd-ee7d-5d63-02da6f95e057@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=tursulin@ursulin.net \
/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