mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alexander A. Klimov" <grandmaster@al2klimov.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"David Heidelberg" <david@ixit.cz>,
	"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio: light: al3320a: read both ALS ADC registers again
Date: Tue, 26 May 2026 20:14:54 +0200	[thread overview]
Message-ID: <f14307bd-060f-4d5a-b7ac-20e9f096463d@al2klimov.de> (raw)
In-Reply-To: <20260526155249.1028be2a@jic23-huawei>



On 5/26/26 16:52, Jonathan Cameron wrote:
> On Sat, 23 May 2026 13:44:58 +0200
> "Alexander A. Klimov" <grandmaster@al2klimov.de> wrote:
> 
>> al3320a_read_raw() used to read two adjacent registers
>> until the driver was modernized using the regmap framework.
>> That cleanup accidentally replaced the 16-bit word read
>> with a single byte read. I'm reverting latter.
>>
>> Fixes: 1850e6ae7f91 ("iio: light: al3320a: Implement regmap support")
>> Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
> For future reference, be careful not to send new threads in reply to
> old ones.

You mean I shall send v2 in the same thread as v1?
Strange...

"please make new threads for everything you send"
  -- greg k-h

https://lore.kernel.org/all/2026052249-shrank-trophy-14ff@gregkh/

  reply	other threads:[~2026-05-28 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 11:44 [PATCH v2] iio: light: al3010: " Alexander A. Klimov
2026-05-23 11:44 ` [PATCH v2] iio: light: al3320a: " Alexander A. Klimov
2026-05-26 14:52   ` Jonathan Cameron
2026-05-26 18:14     ` Alexander A. Klimov [this message]
2026-05-26 14:52 ` [PATCH v2] iio: light: al3010: " 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=f14307bd-060f-4d5a-b7ac-20e9f096463d@al2klimov.de \
    --to=grandmaster@al2klimov.de \
    --cc=andy@kernel.org \
    --cc=david@ixit.cz \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --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®