From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Claudiu <claudiu.beznea@tuxon.dev>,
prabhakar.mahadev-lad.rj@bp.renesas.com, lars@metafoo.de,
linux-iio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH v4 0/2] iio: rzg2l_adc: Cleanups for rzg2l_adc driver
Date: Thu, 27 Mar 2025 17:22:20 +0100 [thread overview]
Message-ID: <2025032703-genre-excitable-9473@gregkh> (raw)
In-Reply-To: <20250327153845.6ab73574@jic23-huawei>
On Thu, Mar 27, 2025 at 03:38:45PM +0000, Jonathan Cameron wrote:
> On Mon, 24 Mar 2025 14:26:25 +0200
> Claudiu <claudiu.beznea@tuxon.dev> wrote:
>
> > From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> >
> > Hi,
> >
> > Series adds some cleanups for the RZ/G2L ADC driver after the support
> > for the RZ/G3S SoC.
>
> This doesn't address Dmitry's comment or highlight the outstanding
> question he had to Greg KH on v3.
> I appreciate you want to get this fixed but I'd rather we got
> it 'right' first time!
>
> Also, please make sure to +CC anyone who engaged with an earlier version.
>
> For reference of Greg if he sees this, Dmitry was expressing view that
> the fix belongs in the bus layer not the individual drivers.
> FWIW that feels like the right layer to me as well.
>
> https://lore.kernel.org/all/Z8k8lDxA53gUJa0n@google.com/#t
As this is a PM question, Rafael would be the best to ask.
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-27 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 12:26 [PATCH v4 0/2] iio: rzg2l_adc: Cleanups for rzg2l_adc driver Claudiu
2025-03-24 12:26 ` [PATCH v4 1/2] iio: adc: rzg2l_adc: Open a devres group Claudiu
2025-03-24 12:26 ` [PATCH v4 2/2] iio: adc: rzg2l: Cleanup suspend/resume path Claudiu
2025-03-27 15:38 ` [PATCH v4 0/2] iio: rzg2l_adc: Cleanups for rzg2l_adc driver Jonathan Cameron
2025-03-27 16:22 ` Greg KH [this message]
2025-03-30 15:36 ` Jonathan Cameron
2025-05-19 9:59 ` Claudiu Beznea
2025-03-27 16:34 ` Claudiu Beznea
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=2025032703-genre-excitable-9473@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=dmitry.torokhov@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.