From: Jonathan Cameron <jic23@kernel.org>
To: Marco Chen <marcochen.dev@gmail.com>
Cc: Joshua Crofts <joshua.crofts1@gmail.com>,
dan@dlrobertson.com, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, jagathjog1996@gmail.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v1] iio: accel: bma400: remove completed tasks from TODO list
Date: Sat, 22 Aug 2026 02:52:58 +0100 [thread overview]
Message-ID: <20260822025258.428c4db9@jic23-huawei> (raw)
In-Reply-To: <aocb9uU4vz4FBo4P@xiaolong>
On Thu, 20 Aug 2026 11:37:49 -0400
Marco Chen <marcochen.dev@gmail.com> wrote:
> On Mon, Aug 17, 2026 at 04:15:23PM +0200, Joshua Crofts wrote:
>
> > Strange that these weren't removed in the commits that introduce said
> > changes... Anyhow, not sure if this patch on its own is too much churn,
> > Jonathan and the other usually prefer these to go in a series of more
> > changes (i.e. if you do the power management TODO, you send this patch
> > in the series). This is up to Jonathan however.
In this case it is tidying up now incorrect documentation. I'm fine
with doing that on it's own. Hence applied.
>
> That makes sense. I will resend this patch as part of a power management
> series instead of an individual patch like I did here. I have ordered
> a bma400 and I am reading the kernel docs on runtime PM and other IIO
> drivers on how they implement it.
>
> To Jonathan, do you have a preference on how the power management
> series should be structured?
Sorry - I'm way behind on review so not going to have time to look at
the datasheet or driver for a few weeks at least. Perhaps share a proposal
and we can look at it on list.
Jonathan
>
>
prev parent reply other threads:[~2026-08-22 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 15:01 [PATCH v1] iio: accel: bma400: remove completed tasks from TODO list Marco Chen
2026-08-17 14:15 ` Joshua Crofts
2026-08-20 15:37 ` Marco Chen
2026-08-22 1:52 ` 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=20260822025258.428c4db9@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dan@dlrobertson.com \
--cc=dlechner@baylibre.com \
--cc=jagathjog1996@gmail.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=marcochen.dev@gmail.com \
--cc=nuno.sa@analog.com \
--cc=skhan@linuxfoundation.org \
/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