dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sunran001@208suo.com
To: airlied@gmail.com, daniel@ffwll.ch
Cc: nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: [PATCH] drm/nouveau: ERROR: (foo*) should be (foo *)
Date: Tue, 11 Jul 2023 14:12:55 +0800	[thread overview]
Message-ID: <d9e5907b772bde22eefb26cb7e0e65e0@208suo.com> (raw)
In-Reply-To: <20230711061131.79666-1-xujianghui@cdjrlc.com>

Fix two occurrences of the checkpatch.pl error:

ERROR: (foo*) should be (foo *)

Signed-off-by: Ran Sun <sunran001@208suo.com>
---
  drivers/gpu/drm/nouveau/nouveau_fence.c | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c 
b/drivers/gpu/drm/nouveau/nouveau_fence.c
index ee5e9d40c166..287885a3a37e 100644
--- a/drivers/gpu/drm/nouveau/nouveau_fence.c
+++ b/drivers/gpu/drm/nouveau/nouveau_fence.c
@@ -169,7 +169,7 @@ nouveau_fence_wait_uevent_handler(struct nvif_event 
*event, void *repv, u32 repc
  void
  nouveau_fence_context_new(struct nouveau_channel *chan, struct 
nouveau_fence_chan *fctx)
  {
-    struct nouveau_fence_priv *priv = (void*)chan->drm->fence;
+    struct nouveau_fence_priv *priv = (void *)chan->drm->fence;
      struct nouveau_cli *cli = (void *)chan->user.client;
      struct {
          struct nvif_event_v0 base;
@@ -207,7 +207,7 @@ int
  nouveau_fence_emit(struct nouveau_fence *fence, struct nouveau_channel 
*chan)
  {
      struct nouveau_fence_chan *fctx = chan->fence;
-    struct nouveau_fence_priv *priv = (void*)chan->drm->fence;
+    struct nouveau_fence_priv *priv = (void *)chan->drm->fence;
      int ret;

      fence->channel  = chan;

           reply	other threads:[~2023-07-11  6:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230711061131.79666-1-xujianghui@cdjrlc.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=d9e5907b772bde22eefb26cb7e0e65e0@208suo.com \
    --to=sunran001@208suo.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@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