From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Jason Wang <wangborong@cdjrlc.com>,
daniel@ffwll.ch, jani.nikula@linux.intel.com,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
tvrtko.ursulin@linux.intel.com, airlied@linux.ie,
John.C.Harrison@intel.com, matthew.d.roper@intel.com,
matthew.brost@intel.com, zhou1615@umn.edu,
michal.winiarski@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/selftests: Fix comment typo
Date: Thu, 21 Jul 2022 15:19:15 +0200 [thread overview]
Message-ID: <YtlSU5uOoGokdKjs@alfio.lan> (raw)
In-Reply-To: <YtlPxPZ/BWATWL1J@alfio.lan>
> On Sat, Jul 16, 2022 at 12:05:20PM +0800, Jason Wang wrote:
> > Fix the double `wait' typo in comment.
> >
> > Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
>
> Few warnings for this patch:
>
> 1. you missed Rodrigo's r-b tag.
> 2. please add a counter to your patch, this would be [PATCH v2]
> 3. please add a changelog, as this is a single patch, do it
> after the '---'
>
> No need to resend, just keep the three notes in mind for your
> next patches. Anyway, thanks for the fix and as I am at it:
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Pushed in drm-intel-next.
Thanks,
Andi
next prev parent reply other threads:[~2022-07-21 13:19 UTC|newest]
Thread overview: 7+ 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
2022-07-21 13:08 ` Andi Shyti
2022-07-21 13:19 ` Andi Shyti [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-15 5:19 Jason Wang
2022-07-18 18:28 ` Rodrigo Vivi
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=YtlSU5uOoGokdKjs@alfio.lan \
--to=andi.shyti@linux.intel.com \
--cc=John.C.Harrison@intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michal.winiarski@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.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