From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Gordon <david.s.gordon@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove redundant return value and WARN_ON
Date: Mon, 3 Nov 2014 14:08:34 +0100 [thread overview]
Message-ID: <20141103130834.GD26941@phenom.ffwll.local> (raw)
In-Reply-To: <1414683716-17376-1-git-send-email-david.s.gordon@intel.com>
On Thu, Oct 30, 2014 at 03:41:56PM +0000, Dave Gordon wrote:
> execlists_submit_context() always returns 0, which is redundant.
> And its name is inaccurate, since it actually submits (up to)
> TWO contextS. So we rename it, change it to "void", and remove
> the WARN_ON() testing its return value.
>
> Change-Id: Ie225b0eca7754c6093c8b8bd15550b251b6feb82
> Signed-off-by: Dave Gordon <david.s.gordon@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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-11-03 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 15:41 [PATCH] drm/i915: Remove redundant return value and WARN_ON Dave Gordon
2014-11-03 13:08 ` 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=20141103130834.GD26941@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=david.s.gordon@intel.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