Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Cc: Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [PATCH 0/4] Trivial style fixes
Date: Fri, 14 Mar 2025 12:10:38 +0000	[thread overview]
Message-ID: <D8FZ8PSKU208.14BXOVT94JCAM@intel.com> (raw)
In-Reply-To: <20250314021225.11813-1-andi.shyti@linux.intel.com>

Hi Andi

On Fri Mar 14, 2025 at 2:12 AM UTC, Andi Shyti wrote:
> Hi
>
> Browsing through my endless list of branches I found a few with
> random cleanups that I fix while rading the code. They tend to be
s/rading/reading

The whole series looks good in my opinion.

Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>

-- 
Best regards,
Sebastian


  parent reply	other threads:[~2025-03-14 12:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14  2:12 [PATCH 0/4] Trivial style fixes Andi Shyti
2025-03-14  2:12 ` [PATCH 1/4] drm/i915/gt: Fix typos in comments Andi Shyti
2025-03-14 13:37   ` Sebastian Brzezinka
2025-03-14 13:41     ` Andi Shyti
2025-03-14  2:12 ` [PATCH 2/4] drm/i915/gt: Fix SPDX license format Andi Shyti
2025-03-18 10:55   ` Krzysztof Karas
2025-03-19  0:34     ` Andi Shyti
2025-03-20  7:38       ` Gote, Nitin R
2025-03-14  2:12 ` [PATCH 3/4] drm/i915/gt: Remove trailing blank lines Andi Shyti
2025-03-20  6:59   ` Gote, Nitin R
2025-03-14  2:12 ` [PATCH 4/4] drm/i915/gt: Use proper sleeping functions for timeouts shorter than 20ms Andi Shyti
2025-03-20  6:54   ` Gote, Nitin R
2025-03-14  4:05 ` ✗ Fi.CI.CHECKPATCH: warning for Trivial style fixes Patchwork
2025-03-14  4:05 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-03-14 12:10 ` Sebastian Brzezinka [this message]
2025-03-18 11:04 ` [PATCH 0/4] " Krzysztof Karas

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=D8FZ8PSKU208.14BXOVT94JCAM@intel.com \
    --to=sebastian.brzezinka@intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=andi.shyti@linux.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