public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: Jason Wang <wangborong@cdjrlc.com>, <daniel@ffwll.ch>,
	<michal.winiarski@intel.com>, <airlied@linux.ie>,
	<intel-gfx@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
	<dri-devel@lists.freedesktop.org>, <zhou1615@umn.edu>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/selftests: Fix comment typo
Date: Thu, 21 Jul 2022 04:08:54 -0400	[thread overview]
Message-ID: <YtkJloZH8kndzKnZ@intel.com> (raw)
In-Reply-To: <d8e59a7f-5eab-3c1b-c8d0-f16e07d63f18@intel.com>

On Wed, Jul 20, 2022 at 06:56:16PM +0200, Andrzej Hajda wrote:
> On 16.07.2022 06:05, Jason Wang wrote:
> > Fix the double `wait' typo in comment.
> > 
> > Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
> > ---
> >   drivers/gpu/drm/i915/selftests/i915_request.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/selftests/i915_request.c b/drivers/gpu/drm/i915/selftests/i915_request.c
> > index c56a0c2cd2f7..ec05f578a698 100644
> > --- a/drivers/gpu/drm/i915/selftests/i915_request.c
> > +++ b/drivers/gpu/drm/i915/selftests/i915_request.c
> > @@ -971,7 +971,7 @@ static struct i915_vma *empty_batch(struct drm_i915_private *i915)
> >   	if (err)
> >   		goto err;
> > -	/* Force the wait wait now to avoid including it in the benchmark */
> > +	/* Force the wait now to avoid including it in the benchmark */
> >   	err = i915_vma_sync(vma);
> >   	if (err)
> >   		goto err_pin;
> 
> Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>

Thanks for the patch and review. Pushed to drm-intel-gt-next.

> 
> Regards
> Andrzej

  reply	other threads:[~2022-07-21  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16  4:05 [PATCH] drm/i915/selftests: Fix comment typo Jason Wang
2022-07-20 16:56 ` [Intel-gfx] " Andrzej Hajda
2022-07-21  8:08   ` Rodrigo Vivi [this message]
2022-07-21 13:08 ` Andi Shyti
2022-07-21 13:19   ` Andi Shyti

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=YtkJloZH8kndzKnZ@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@linux.ie \
    --cc=andrzej.hajda@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.winiarski@intel.com \
    --cc=wangborong@cdjrlc.com \
    --cc=zhou1615@umn.edu \
    /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