Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
	linux-iio@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] iio: light: isl76682: Space consistency
Date: Wed, 6 Dec 2023 17:21:57 +0000	[thread overview]
Message-ID: <20231206172157.24439ca4@jic23-huawei> (raw)
In-Reply-To: <26aa7753-c597-4e5d-afd3-a407e5605335@gmail.com>

On Tue, 5 Dec 2023 09:21:02 +0200
Matti Vaittinen <mazziesaccount@gmail.com> wrote:

> On 12/5/23 03:22, Marek Vasut wrote:
> > Add missing space between { } to be consistent with the other { } .
> > No functional change.
> > 
> > Signed-off-by: Marek Vasut <marex@denx.de>  
> 
> Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
> 
I squashed this into the driver patch.

Thanks,

Jonathan

> > ---
> > Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Cc: Jonathan Cameron <jic23@kernel.org>
> > Cc: Lars-Peter Clausen <lars@metafoo.de>
> > Cc: Matti Vaittinen <mazziesaccount@gmail.com>
> > Cc: linux-iio@vger.kernel.org
> > ---
> >   drivers/iio/light/isl76682.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/iio/light/isl76682.c b/drivers/iio/light/isl76682.c
> > index 15a68609985b6..a17970fb3758e 100644
> > --- a/drivers/iio/light/isl76682.c
> > +++ b/drivers/iio/light/isl76682.c
> > @@ -328,7 +328,7 @@ static int isl76682_probe(struct i2c_client *client)
> >   
> >   static const struct i2c_device_id isl76682_id[] = {
> >   	{ "isl76682" },
> > -	{}
> > +	{ }
> >   };
> >   MODULE_DEVICE_TABLE(i2c, isl76682_id);
> >     
> 


      reply	other threads:[~2023-12-06 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  1:22 [PATCH] iio: light: isl76682: Space consistency Marek Vasut
2023-12-05  7:21 ` Matti Vaittinen
2023-12-06 17:21   ` Jonathan Cameron [this message]

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=20231206172157.24439ca4@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=mazziesaccount@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