public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Devos <ndevos-dev@pm.me>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: Nicolas Devos <ndevos-dev@pm.me>
Subject: [PATCH 0/4] gpu/drm: Fix checkpatch warnings in drm_connector.c
Date: Tue, 02 Apr 2024 22:43:30 +0000	[thread overview]
Message-ID: <20240402224320.12146-1-ndevos-dev@pm.me> (raw)

Hello,

First time contributor here, I am getting familiar with the flow by
fixing some checkpatch warnings. This patch series fixes the warnings of
drivers/gpu/drm/drm_connector.c.

The result is 4 patches that each address a separate issue raised by
the checkpatch.pl script.

My initial attempt [1] was not accepted, this patch series addresses the
given review comments.

Please, let me know if something is not as expected.

[1]: https://lore.kernel.org/all/20240222204450.7943-1-ndevos-dev@pm.me/

Nicolas Devos (4):
  gpu/drm: Add SPDX-license-Identifier tag
  gpu/drm: Remove unnecessary braces
  gpu/drm: Prefer `unsigned int` over `unsigned`
  gpu/drm: Replace tabs with spaces in comments

 drivers/gpu/drm/drm_connector.c | 722 ++++++++++++++++----------------
 1 file changed, 361 insertions(+), 361 deletions(-)

-- 
2.42.0



             reply	other threads:[~2024-04-02 22:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 22:43 Nicolas Devos [this message]
2024-04-02 22:43 ` [PATCH 1/4] gpu/drm: Add SPDX-license-Identifier tag Nicolas Devos
2024-04-02 23:58   ` Joe Perches
2024-04-02 22:43 ` [PATCH 2/4] gpu/drm: Remove unnecessary braces Nicolas Devos
2024-04-02 22:43 ` [PATCH 3/4] gpu/drm: Prefer `unsigned int` over `unsigned` Nicolas Devos
2024-04-02 22:43 ` [PATCH 4/4] gpu/drm: Replace tabs with spaces in comments Nicolas Devos

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=20240402224320.12146-1-ndevos-dev@pm.me \
    --to=ndevos-dev@pm.me \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox