From: Jonathan Santos <jonath4nns@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Jonathan Santos <Jonathan.Santos@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, lars@metafoo.de,
Michael.Hennerich@analog.com, marcelo.schmitt@analog.com,
jic23@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, marcelo.schmitt1@gmail.com
Subject: Re: [PATCH v3 05/17] dt-bindings: iio: adc: ad7768-1: document regulator provider property
Date: Wed, 12 Feb 2025 12:01:27 -0300 [thread overview]
Message-ID: <Z6y3x6WYCdTmXo3X@JSANTO12-L01.ad.analog.com> (raw)
In-Reply-To: <20250212-dazzling-glaring-shrimp-9530e6@krzk-bin>
On 02/12, Krzysztof Kozlowski wrote:
> On Tue, Feb 11, 2025 at 08:47:16PM -0300, Jonathan Santos wrote:
> > The AD7768-1 provides a buffered common-mode voltage output
> > on the VCM pin that can be used to bias analog input signals.
> >
> > Add regulators property to enable the use of the VCM output,
> > referenced here as vcm_output, by any other device.
> >
> > Signed-off-by: Jonathan Santos <Jonathan.Santos@analog.com>
> > ---
> > v3 Changes:
> > * VCM is now provided as a regulator within the device, instead of a
> > custom property.
> >
> > v2 Changes:
> > * New patch in v2.
>
> There is some mess in this posting. Nothing looks threaded and b4 does
> not see entire posting.
>
> Sorry, don't make it complicated to us. Send proper submission - see
> numorous guides or submitting-patches - so reviewing will be
> straightforward.
>
> Best regards,
> Krzysztof
I am sorry about that, my mistake. I missed the --thread option
when creating the patches. I will resend them properly.
Apologies,
Jonathan S.
>
prev parent reply other threads:[~2025-02-12 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 23:47 Jonathan Santos
2025-02-12 7:17 ` Krzysztof Kozlowski
2025-02-12 15:01 ` Jonathan Santos [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=Z6y3x6WYCdTmXo3X@JSANTO12-L01.ad.analog.com \
--to=jonath4nns@gmail.com \
--cc=20250212-dazzling-glaring-shrimp-9530e6@krzk-bin \
--cc=Jonathan.Santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=robh@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
all inboxes | Powered by JetHome®