Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Neel Bullywon <neelb2403@gmail.com>,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 3/3] iio: magnetometer: bmc150_magn: minor formatting cleanup
Date: Fri, 20 Feb 2026 10:37:36 +0000	[thread overview]
Message-ID: <20260220103736.70639aa8@jic23-huawei> (raw)
In-Reply-To: <aZLWu_7ozsmUZbtg@smile.fi.intel.com>

On Mon, 16 Feb 2026 10:35:07 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Sun, Feb 15, 2026 at 08:54:54PM -0500, Neel Bullywon wrote:
> > Improve initializer list style for bmc150_magn_samp_freq_table by
> > moving the opening brace to its own line and using one entry per line
> > with proper indentation and spaces inside braces.
> > 
> > Add spaces inside braces for initializer lists in the preset table
> > for consistency.
> > 
> > Fix indentation of bmc150_magn_scan_masks array. No functional changes.  
> 
> LGTM, FWIW,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> 

This is also independent of patch 1 so I've picked it up now.

Applied to the testing branch of iio.git

Thanks,

Jonathan

      reply	other threads:[~2026-02-20 10:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16  1:54 [PATCH v7 0/3] iio: magnetometer: bmc150_magn: cleanup and formatting Neel Bullywon
2026-02-16  1:54 ` [PATCH v7 1/3] iio: magnetometer: bmc150_magn: use automated cleanup for mutex Neel Bullywon
2026-02-16  8:33   ` Andy Shevchenko
2026-02-20 10:34     ` Jonathan Cameron
2026-02-20 19:29       ` Neel Bullywon
2026-02-16  1:54 ` [PATCH v7 2/3] iio: magnetometer: bmc150_magn: replace msleep with fsleep Neel Bullywon
2026-02-20 10:37   ` Jonathan Cameron
2026-02-16  1:54 ` [PATCH v7 3/3] iio: magnetometer: bmc150_magn: minor formatting cleanup Neel Bullywon
2026-02-16  8:35   ` Andy Shevchenko
2026-02-20 10:37     ` 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=20260220103736.70639aa8@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neelb2403@gmail.com \
    --cc=nuno.sa@analog.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