mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Arnav Kapoor <kapoorarnav43@gmail.com>
Cc: Joshua Crofts <joshua.crofts1@gmail.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Benson Leung <bleung@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	David Lechner <dlechner@baylibre.com>,
	Nuno Sa <nuno.sa@analog.com>, Andy Shevchenko <andy@kernel.org>,
	chrome-platform@lists.linux.dev, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: common: cros_ec_sensors: use sensor_scale union member for CALIBSCALE
Date: Tue, 13 Oct 2026 22:55:27 +0300	[thread overview]
Message-ID: <as6Mr7BSbJeJRlBq@ashevche-desk.local> (raw)
In-Reply-To: <20261012211733.575305-1-kapoorarnav43@gmail.com>

On Tue, Oct 13, 2026 at 02:47:30AM +0530, Arnav Kapoor wrote:
> On Sun, 11 Oct 2026 19:16:41 +0200, Joshua Crofts wrote:
> > Please add a Fixes tag. Otherwise looks good to me!
> >
> > Reviewed-by: Joshua Crofts <joshua.crofts1@gmail.com>
> 
> Thanks for the review. The mismatch was introduced when CALIBSCALE
> support was added:
> 
> Fixes: ed1f2e85da79 ("iio: cros_ec: Add calibscale for 3d MEMS")
> 
> Jonathan, could you pick this up when applying, or would you prefer a v2?

No need to resend, `b4` will scan the whole email thread for the tags.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-10-13 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11  4:54 Arnav Kapoor
2026-10-11 17:16 ` Joshua Crofts
2026-10-12 21:17   ` Arnav Kapoor
2026-10-13 19:55     ` Andy Shevchenko [this message]
2026-10-17 23:02       ` Jonathan Cameron
2026-10-18  7:05         ` Tzung-Bi Shih
2026-10-18 18:09           ` 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=as6Mr7BSbJeJRlBq@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=dlechner@baylibre.com \
    --cc=groeck@chromium.org \
    --cc=jic23@kernel.org \
    --cc=joshua.crofts1@gmail.com \
    --cc=kapoorarnav43@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®