All of lore.kernel.org
 help / color / mirror / Atom feed
From: Beatriz Martins de Carvalho <martinsdecarvalhobeatriz@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@linux.ie, daniel@ffwll.ch,
	dri-devel@lists.freedesktop.org,
	outreachy-kernel@googlegroups.com
Cc: Beatriz Martins de Carvalho <martinsdecarvalhobeatriz@gmail.com>
Subject: [PATCH 0/5] drm: Adjust end of block comment
Date: Sun, 18 Apr 2021 15:48:20 +0100	[thread overview]
Message-ID: <cover.1618756333.git.martinsdecarvalhobeatriz@gmail.com> (raw)

Add a new line with */ on the last line of a block comment to follow 
the Linux kernel coding conventions. 
Problem found by checkpatch.
in tree dpu/drm

Beatriz Martins de Carvalho (5):
  drm: drm_atomic.c: Adjust end of block comment
  drm: drm_auth.c: Adjust end of block comment
  drm: drm_bufs.c: Adjust end of block comment
  drm: drm_connector.c: Adjust end of block comment
  drm: drm_context.c: Adjust end of block comment

 drivers/gpu/drm/drm_atomic.c    | 3 ++-
 drivers/gpu/drm/drm_auth.c      | 3 ++-
 drivers/gpu/drm/drm_bufs.c      | 3 ++-
 drivers/gpu/drm/drm_connector.c | 9 ++++++---
 drivers/gpu/drm/drm_context.c   | 3 ++-
 5 files changed, 14 insertions(+), 7 deletions(-)

-- 
2.25.1



WARNING: multiple messages have this Message-ID (diff)
From: Beatriz Martins de Carvalho <martinsdecarvalhobeatriz@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@linux.ie, daniel@ffwll.ch
Cc: melissa.srw@gmail.com, outreachy-kernel@googlegroups.com,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH 0/5] drm: Adjust end of block comment
Date: Wed, 21 Apr 2021 20:46:53 +0100	[thread overview]
Message-ID: <cover.1618756333.git.martinsdecarvalhobeatriz@gmail.com> (raw)

Add a new line with */ on the last line of a block comment to follow 
the Linux kernel coding conventions. 
Problem found by checkpatch.
in tree dpu/drm

Beatriz Martins de Carvalho (5):
  drm: drm_atomic.c: Adjust end of block comment
  drm: drm_auth.c: Adjust end of block comment
  drm: drm_bufs.c: Adjust end of block comment
  drm: drm_connector.c: Adjust end of block comment
  drm: drm_context.c: Adjust end of block comment

 drivers/gpu/drm/drm_atomic.c    | 3 ++-
 drivers/gpu/drm/drm_auth.c      | 3 ++-
 drivers/gpu/drm/drm_bufs.c      | 3 ++-
 drivers/gpu/drm/drm_connector.c | 9 ++++++---
 drivers/gpu/drm/drm_context.c   | 3 ++-
 5 files changed, 14 insertions(+), 7 deletions(-)

-- 
2.25.1

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Beatriz Martins de Carvalho <martinsdecarvalhobeatriz@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@linux.ie, daniel@ffwll.ch
Cc: melissa.srw@gmail.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: [PATCH 0/5] drm: Adjust end of block comment
Date: Wed, 21 Apr 2021 20:46:53 +0100	[thread overview]
Message-ID: <cover.1618756333.git.martinsdecarvalhobeatriz@gmail.com> (raw)

Add a new line with */ on the last line of a block comment to follow 
the Linux kernel coding conventions. 
Problem found by checkpatch.
in tree dpu/drm

Beatriz Martins de Carvalho (5):
  drm: drm_atomic.c: Adjust end of block comment
  drm: drm_auth.c: Adjust end of block comment
  drm: drm_bufs.c: Adjust end of block comment
  drm: drm_connector.c: Adjust end of block comment
  drm: drm_context.c: Adjust end of block comment

 drivers/gpu/drm/drm_atomic.c    | 3 ++-
 drivers/gpu/drm/drm_auth.c      | 3 ++-
 drivers/gpu/drm/drm_bufs.c      | 3 ++-
 drivers/gpu/drm/drm_connector.c | 9 ++++++---
 drivers/gpu/drm/drm_context.c   | 3 ++-
 5 files changed, 14 insertions(+), 7 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-04-19  6:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 14:48 Beatriz Martins de Carvalho [this message]
2021-04-21 19:46 ` [PATCH 0/5] drm: Adjust end of block comment Beatriz Martins de Carvalho
2021-04-21 19:46 ` Beatriz Martins de Carvalho
2021-04-18 14:48 ` [PATCH 1/5] drm: drm_atomic.c: " Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-18 14:48 ` [PATCH 2/5] drm: drm_auth.c: " Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-18 14:48 ` [PATCH 3/5] drm: drm_bufs.c: " Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-18 14:48 ` [PATCH 4/5] drm: drm_connector.c: " Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-18 14:48 ` [PATCH 5/5] drm: drm_context.c: " Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho
2021-04-21 19:46   ` Beatriz Martins de Carvalho

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=cover.1618756333.git.martinsdecarvalhobeatriz@gmail.com \
    --to=martinsdecarvalhobeatriz@gmail.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.