Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Gwendal Grignou <gwendal@chromium.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Andreas Klinger <ak@it-klinger.de>
Subject: [PATCH 06/16] iio:proximity:ping: White space cleanup of spacing around {} in id tables
Date: Thu, 30 Dec 2021 17:49:01 +0000	[thread overview]
Message-ID: <20211230174911.78291-7-jic23@kernel.org> (raw)
In-Reply-To: <20211230174911.78291-1-jic23@kernel.org>

From: Jonathan Cameron <Jonathan.Cameron@huawei.com>

The spacing in this driver was inconsistent so make sure we have a space
after { and before } for the two id tables.
Avoid providing examples of this inconsistency that get copied into new
drivers.

Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Andreas Klinger <ak@it-klinger.de>
---
 drivers/iio/proximity/ping.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/iio/proximity/ping.c b/drivers/iio/proximity/ping.c
index 1283ac1c2e03..24a97d41e115 100644
--- a/drivers/iio/proximity/ping.c
+++ b/drivers/iio/proximity/ping.c
@@ -267,8 +267,8 @@ static const struct iio_chan_spec ping_chan_spec[] = {
 };
 
 static const struct of_device_id of_ping_match[] = {
-	{ .compatible = "parallax,ping", .data = &pa_ping_cfg},
-	{ .compatible = "parallax,laserping", .data = &pa_laser_ping_cfg},
+	{ .compatible = "parallax,ping", .data = &pa_ping_cfg },
+	{ .compatible = "parallax,laserping", .data = &pa_laser_ping_cfg },
 	{},
 };
 
-- 
2.34.1


  parent reply	other threads:[~2021-12-30 17:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 17:48 [PATCH 00/16] IIO: Tidy up inconsistent spacing in ID tables Jonathan Cameron
2021-12-30 17:48 ` [PATCH 01/16] iio:chemical:atlas: Trivial white space cleanup to add space before } Jonathan Cameron
2021-12-31  5:46   ` Gwendal Grignou
2021-12-30 17:48 ` [PATCH 02/16] iio:light:pa12203001: Tidy up white space change to add spaces after { and " Jonathan Cameron
2021-12-31  5:45   ` Gwendal Grignou
2021-12-30 17:48 ` [PATCH 03/16] iio:light:vcnl4035: Trivial whitespace cleanup to add space " Jonathan Cameron
2021-12-31  5:46   ` Gwendal Grignou
2021-12-30 17:48 ` [PATCH 04/16] iio:light:us5182: White space cleanup of spacing around {} in id tables Jonathan Cameron
2021-12-31  5:47   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 05/16] iio:light:ltr501: " Jonathan Cameron
2021-12-31  5:47   ` Gwendal Grignou
2021-12-30 17:49 ` Jonathan Cameron [this message]
2021-12-31  5:48   ` [PATCH 06/16] iio:proximity:ping: " Gwendal Grignou
2021-12-30 17:49 ` [PATCH 07/16] iio:proximity:rfd77402: " Jonathan Cameron
2021-12-31  5:48   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 08/16] iio:proximity:srf04: " Jonathan Cameron
2021-12-31  5:48   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 09/16] iio:proximity:srf08: " Jonathan Cameron
2021-12-31  5:49   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 10/16] iio:frequency:admv1013: " Jonathan Cameron
2021-12-31  5:49   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 11/16] iio:adc:mt6577_auxadc: Tidy up white space " Jonathan Cameron
2021-12-31  5:49   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 12/16] iio:adc:hi8435: " Jonathan Cameron
2021-12-31  5:49   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 13/16] iio:adc:ti-adc084s021: Tidy up white space around {} Jonathan Cameron
2021-12-31  5:50   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 14/16] iio:light:tsl2722: Fix inconsistent spacing before } in id table Jonathan Cameron
2021-12-31  5:50   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 15/16] iio:proximity:vl53l0x: Tidy up white space around {} in id tables Jonathan Cameron
2021-12-31  5:50   ` Gwendal Grignou
2021-12-30 17:49 ` [PATCH 16/16] iio:accel:dmard09: Tidy up white space around {} in id table Jonathan Cameron
2021-12-31  5:50   ` Gwendal Grignou
2022-01-09 15:00 ` [PATCH 00/16] IIO: Tidy up inconsistent spacing in ID tables Jonathan Cameron

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=20211230174911.78291-7-jic23@kernel.org \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=ak@it-klinger.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=gwendal@chromium.org \
    --cc=linux-iio@vger.kernel.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