dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Jamal Shareef" <jamal.k.shareef@gmail.com>
Cc: outreachy-kernel@googlegroups.com, 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
Subject: Re: [PATCH 0/3] drm/tegra: Remove space after parenthesis
Date: Mon, 04 Nov 2019 20:59:43 -0800	[thread overview]
Message-ID: <4df246124153bcece639fdd026c4eee629b4bb7a.camel@perches.com> (raw)
In-Reply-To: <20191105045337.GB1764@qmqm.qmqm.pl>

On Tue, 2019-11-05 at 05:53 +0100, Michał Mirosław wrote:
> On Mon, Nov 04, 2019 at 06:23:19PM -0800, Jamal Shareef wrote:
> > This patchset removes spaces after left open parenthesis.
> > Issue found by checkpatch.
> 
> I'd say that those spaces make code easier to look at, so it would
> be better to teach checkpatch to ignore cases like these.

Good luck with that.

WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Jamal Shareef" <jamal.k.shareef@gmail.com>
Cc: airlied@linux.ie, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, jonathanh@nvidia.com,
	outreachy-kernel@googlegroups.com, thierry.reding@gmail.com,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/3] drm/tegra: Remove space after parenthesis
Date: Mon, 04 Nov 2019 20:59:43 -0800	[thread overview]
Message-ID: <4df246124153bcece639fdd026c4eee629b4bb7a.camel@perches.com> (raw)
Message-ID: <20191105045943.9kjDnkKsZtMV8aBy28HtR6-Ifwh0QUir7OhMUDvK0Zg@z> (raw)
In-Reply-To: <20191105045337.GB1764@qmqm.qmqm.pl>

On Tue, 2019-11-05 at 05:53 +0100, Michał Mirosław wrote:
> On Mon, Nov 04, 2019 at 06:23:19PM -0800, Jamal Shareef wrote:
> > This patchset removes spaces after left open parenthesis.
> > Issue found by checkpatch.
> 
> I'd say that those spaces make code easier to look at, so it would
> be better to teach checkpatch to ignore cases like these.

Good luck with that.


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

  parent reply	other threads:[~2019-11-05  4:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  2:23 [PATCH 0/3] drm/tegra: Remove space after parenthesis Jamal Shareef
2019-11-05  2:23 ` 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:59   ` Joe Perches [this message]
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=4df246124153bcece639fdd026c4eee629b4bb7a.camel@perches.com \
    --to=joe@perches.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jamal.k.shareef@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox