From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: 1064094935@qq.com, Jani Nikula <jani.nikula@linux.intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, pengfuyuan <pengfuyuan@kylinos.cn>,
k2ci <kernel-bot@kylinos.cn>
Subject: Re: [PATCH] drm/i915: Fix spelling typo in comment
Date: Wed, 22 Jun 2022 07:53:05 +0100 [thread overview]
Message-ID: <529b043a-e6af-cd1c-c6b8-a7778c2799d0@linux.intel.com> (raw)
In-Reply-To: <tencent_7B226C4A9BC2B5EEB37B70C188B5015D290A@qq.com>
On 16/06/2022 08:08, 1064094935@qq.com wrote:
> From: pengfuyuan <pengfuyuan@kylinos.cn>
>
> Fix spelling typo in comment.
>
> Reported-by: k2ci <kernel-bot@kylinos.cn>
> Signed-off-by: pengfuyuan <pengfuyuan@kylinos.cn>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_tiling.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_tiling.c b/drivers/gpu/drm/i915/gem/i915_gem_tiling.c
> index 80ac0db1ae8c..85518b28cd72 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_tiling.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_tiling.c
> @@ -114,7 +114,7 @@ u32 i915_gem_fence_alignment(struct drm_i915_private *i915, u32 size,
> return i915_gem_fence_size(i915, size, tiling, stride);
> }
>
> -/* Check pitch constriants for all chips & tiling formats */
> +/* Check pitch constraints for all chips & tiling formats */
> static bool
> i915_tiling_ok(struct drm_i915_gem_object *obj,
> unsigned int tiling, unsigned int stride)
Merged to drm-intel-gt-next - thanks for the patch!
Regards,
Tvrtko
parent reply other threads:[~2022-06-22 6:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_7B226C4A9BC2B5EEB37B70C188B5015D290A@qq.com>]
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=529b043a-e6af-cd1c-c6b8-a7778c2799d0@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=1064094935@qq.com \
--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=kernel-bot@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=pengfuyuan@kylinos.cn \
--cc=rodrigo.vivi@intel.com \
/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