public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Maxwell Doose" <m32285159@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>,
	"Maxwell Doose" <m32285159@gmail.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
	songqiang1304521@gmail.com,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"open list:PNI RM3100 IIO DRIVER" <linux-iio@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] iio: magnetometer: rm3100: Modernize locking and refactor control flow
Date: Wed, 06 May 2026 10:28:29 -0500	[thread overview]
Message-ID: <DIBP7X7GR2EW.15FM732PJ1WOX@gmail.com> (raw)
In-Reply-To: <20260506154347.19e7d68f@jic23-huawei>

On Wed May 6, 2026 at 9:43 AM CDT, Jonathan Cameron wrote:
> On Tue, 5 May 2026 12:05:11 -0500
> Maxwell Doose <m32285159@gmail.com> wrote:
>
>> On Tue, May 5, 2026 at 7:45 AM Jonathan Cameron <jic23@kernel.org> wrote:
>> >
>> > Applied to the testing branch of iio.git with that tweak.
>> >
>> > Thanks,
>> >
>> > Jonathan
>> >  
>> 
>> Hey Jonathan, I just noticed that I made a mistake in the commit
>> message, it says "Add new helper-wrapper function
>> rm3100_guarded_regmap_bulk_read()..." when it really should be "Add
>> new helper-wrapper function rm3100_regmap_bulk_read_locked()..." I'm
>> unfortunately not in a position to fix it myself since I'm away, but I
>> just wanted to point it out so it could be fixed.
> fixed up.
>> 
>> best regards,
>> max

Gosh, I'm so sorry to keep bothering you, but I noticed a stray change
here:

@@ -7,7 +7,7 @@
  * User Manual available at
  * <https://www.pnicorp.com/download/rm3100-user-manual/>
  *
- * TODO: event generation, pm.
+ * TODO: event generation, pm.da
  */

wishing vs code would quit messing with me,
max

  reply	other threads:[~2026-05-06 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 12:41 [PATCH v5] iio: magnetometer: rm3100: Modernize locking and refactor control flow Maxwell Doose
2026-04-30 12:45 ` Maxwell Doose
2026-04-30 12:57 ` Andy Shevchenko
2026-04-30 15:43   ` Maxwell Doose
2026-05-05 12:45     ` Jonathan Cameron
2026-05-05 17:05       ` Maxwell Doose
2026-05-06 14:43         ` Jonathan Cameron
2026-05-06 15:28           ` Maxwell Doose [this message]
2026-05-06 18:31             ` 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=DIBP7X7GR2EW.15FM732PJ1WOX@gmail.com \
    --to=m32285159@gmail.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --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 \
    --cc=songqiang1304521@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