From: Jonathan Cameron <jic23@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Andreas Kemnade <andreas@kemnade.info>,
lars@metafoo.de, sre@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
letux-kernel@openphoenux.org
Subject: Re: [PATCH v3 0/2] mfd: rn5t618: Extend ADC support
Date: Sat, 17 Jul 2021 18:08:02 +0100 [thread overview]
Message-ID: <20210717180802.7261d8bb@jic23-huawei> (raw)
In-Reply-To: <YO1Ob18YsDdEMfuf@google.com>
On Tue, 13 Jul 2021 09:27:27 +0100
Lee Jones <lee.jones@linaro.org> wrote:
> On Mon, 12 Jul 2021, Andreas Kemnade wrote:
>
> > Add iio map to make voltage_now related channels accessible to power
> > driver.
> >
> > Changes in v3:
> > - use scale functions
> > - add acks
> >
> > Changes in v2:
> > - use iio_map instead of devicetree to allow mapping which does not
> > block future extension by devicetree.
> >
> >
> > *** BLURB HERE ***
>
> Doh!
>
> > Andreas Kemnade (2):
> > iio: adc: rn5t618: Add iio map
> > power: supply: rn5t618: Add voltage_now property
> >
> > drivers/iio/adc/rn5t618-adc.c | 23 +++++++++++++++++
> > drivers/power/supply/Kconfig | 2 ++
> > drivers/power/supply/rn5t618_power.c | 38 ++++++++++++++++++++++++++++
> > 3 files changed, 63 insertions(+)
>
> Not sure I get this.
>
> Firstly, the cover-letter is marked as MFD, but no MFD changes occur.
So this is a bit of a fun corner case. The series 'used' to include an mfd
change that made that labelling relevant. Then that went away as I suggested
that we could do it in a simpler fashion.
Under the circumstances the series needed a rename!
> Secondly, I am only in receipt of the 0th patch which seems odd. IMHO
> patch sets should be sent threaded and all parties should see
> discussion on all patches regardless of whether they maintain them or
> not, since the overall conversation is often useful/relevant to all.
>
Absolutely agree for small series like this.
Anyhow, as far as I'm concerned this is now in the hands of the power supply
maintainers anyway so ignoring it ;)
Jonathan
next prev parent reply other threads:[~2021-07-17 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 21:21 [PATCH v3 0/2] mfd: rn5t618: Extend ADC support Andreas Kemnade
2021-07-12 21:21 ` [PATCH v3 1/2] iio: adc: rn5t618: Add iio map Andreas Kemnade
2021-07-12 21:21 ` [PATCH v3 2/2] power: supply: rn5t618: Add voltage_now property Andreas Kemnade
2021-07-13 8:27 ` [PATCH v3 0/2] mfd: rn5t618: Extend ADC support Lee Jones
2021-07-17 17:08 ` Jonathan Cameron [this message]
2021-08-13 16:00 ` Sebastian Reichel
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=20210717180802.7261d8bb@jic23-huawei \
--to=jic23@kernel.org \
--cc=andreas@kemnade.info \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.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;
as well as URLs for NNTP newsgroup(s).