From: Jamal Shareef <jamal.k.shareef@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: thierry.reding@gmail.com, airlied@linux.ie, daniel@ffwll.ch,
jonathanh@nvidia.com, dri-devel@lists.freedesktop.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Jamal Shareef <jamal.k.shareef@gmail.com>
Subject: [PATCH 0/3] drm/tegra: Remove space after parenthesis
Date: Mon, 4 Nov 2019 18:23:19 -0800 [thread overview]
Message-ID: <cover.1572920482.git.jamal.k.shareef@gmail.com> (raw)
This patchset removes spaces after left open parenthesis.
Issue found by checkpatch.
Jamal Shareef (3):
drm/tegra: dc: Remove space after parenthesis
drm/tegra: dsi: Remove space in open parenthesis
drm/tegra: gr3d: Remove space after parenthesis
drivers/gpu/drm/tegra/dc.h | 40 ++++++------
drivers/gpu/drm/tegra/dsi.c | 60 +++++++++---------
drivers/gpu/drm/tegra/gr3d.c | 120 +++++++++++++++++------------------
3 files changed, 110 insertions(+), 110 deletions(-)
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Jamal Shareef <jamal.k.shareef@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: airlied@linux.ie, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, jonathanh@nvidia.com,
thierry.reding@gmail.com, linux-tegra@vger.kernel.org,
Jamal Shareef <jamal.k.shareef@gmail.com>
Subject: [PATCH 0/3] drm/tegra: Remove space after parenthesis
Date: Mon, 4 Nov 2019 18:23:19 -0800 [thread overview]
Message-ID: <cover.1572920482.git.jamal.k.shareef@gmail.com> (raw)
Message-ID: <20191105022319.1_LTx7GXR5QCm3wruDXSRb570u1KZQAUWaUCb1Y3vf8@z> (raw)
This patchset removes spaces after left open parenthesis.
Issue found by checkpatch.
Jamal Shareef (3):
drm/tegra: dc: Remove space after parenthesis
drm/tegra: dsi: Remove space in open parenthesis
drm/tegra: gr3d: Remove space after parenthesis
drivers/gpu/drm/tegra/dc.h | 40 ++++++------
drivers/gpu/drm/tegra/dsi.c | 60 +++++++++---------
drivers/gpu/drm/tegra/gr3d.c | 120 +++++++++++++++++------------------
3 files changed, 110 insertions(+), 110 deletions(-)
--
2.17.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-11-05 2:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 2:23 Jamal Shareef [this message]
2019-11-05 2:23 ` [PATCH 0/3] drm/tegra: Remove space after parenthesis Jamal Shareef
2019-11-05 2:23 ` [PATCH 1/3] drm/tegra: dc: " Jamal Shareef
2019-11-05 2:23 ` Jamal Shareef
2019-11-05 2:23 ` [PATCH 2/3] drm/tegra: dsi: Remove space in open parenthesis Jamal Shareef
2019-11-05 2:23 ` Jamal Shareef
2019-11-05 2:23 ` [PATCH 3/3] drm/tegra: gr3d: Remove space after parenthesis Jamal Shareef
2019-11-05 2:23 ` Jamal Shareef
2019-11-05 4:53 ` [PATCH 0/3] drm/tegra: " Michał Mirosław
2019-11-05 4:53 ` Michał Mirosław
2019-11-05 4:53 ` Michał Mirosław
2019-11-05 4:59 ` Joe Perches
2019-11-05 4:59 ` Joe Perches
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.1572920482.git.jamal.k.shareef@gmail.com \
--to=jamal.k.shareef@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=thierry.reding@gmail.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 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.