public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Janani Sunil <jan.sun97@gmail.com>
Cc: Jonathan Cameron <jonathan.cameron@huawei.com>,
	Janani Sunil <janani.sunil@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Alexandru Ardelean <alexandru.ardelean@analog.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	gastmaier@gmail.com
Subject: Re: [PATCH 3/3] iio: dac: Add MAX22007 DAC driver support
Date: Sun, 11 Jan 2026 11:50:17 +0000	[thread overview]
Message-ID: <20260111115017.62802a56@jic23-huawei> (raw)
In-Reply-To: <013a144f-101e-49dd-9865-79dd6181f43a@gmail.com>

On Wed, 7 Jan 2026 16:28:31 +0100
Janani Sunil <jan.sun97@gmail.com> wrote:

> Hi Jonathan,
> 
> Thank you for your review.
> 
> On 12/19/25 18:25, Jonathan Cameron wrote:
> > On Fri, 19 Dec 2025 16:31:17 +0100
> > Janani Sunil <janani.sunil@analog.com> wrote:
> >  
> >> Add support for the MAX22007 4 channel DAC
> >> that drives a voltage or current output on each channel.  
> > wrap to 75 chars rather than 50-60ish  
> 
> Noted. Will correct this.
> 
> >> Signed-off-by: Janani Sunil <janani.sunil@analog.com>  
> > Hi Janani
> >
> > A few minor things inline.  Also add turning on any required
> > power supplies.  See how other drivers do it with a single call
> > in in probe. If your board is using always on supplies it will just
> > work as a stub regulator will be provided by the regulator core.
> >
> >
> > Thanks,
> >
> > Jonathan  
> 
> Will take a reference from the other drivers and add the power supply configurations.

Hi Janani,

A small process thing you should take into account for future replies.
Generally kernel mailing lists are very high volume with a lot of review
feedback. As such we tend to go for a balance of efficiency over politeness.

So when you agree to a particular bit of feedback, just crop out that
bit of the message in any reply (if you agree to all of it no need to reply at
all!).  That lets us focus in quickly on the bits that need more discussion.

The politeness bit is resolve by adding a thank alongside the change log
in the next version.  I end up sending this message to someone most weeks,
so don't worry about it!  It feels unnatural to all of us initially.

Thanks

Jonathan


      reply	other threads:[~2026-01-11 11:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 15:31 [PATCH 0/3] Subject: [PATCH v1 0/3] iio: dac: Add support for MAX22007 DAC Janani Sunil
2025-12-19 15:31 ` [PATCH 1/3] dt-bindings: iio: dac: Add max22007 Janani Sunil
2025-12-19 15:50   ` Krzysztof Kozlowski
2026-01-07 15:13     ` Janani Sunil
2025-12-19 16:40   ` Jonathan Cameron
2026-01-07 15:18     ` Janani Sunil
2025-12-19 15:31 ` [PATCH 2/3] docs: iio: Add documentation for MAX22007 driver Janani Sunil
2025-12-19 16:47   ` Jonathan Cameron
2026-01-07 15:20     ` Janani Sunil
2025-12-19 15:31 ` [PATCH 3/3] iio: dac: Add MAX22007 DAC driver support Janani Sunil
2025-12-19 17:25   ` Jonathan Cameron
2026-01-07 15:28     ` Janani Sunil
2026-01-11 11:50       ` 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=20260111115017.62802a56@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=alexandru.ardelean@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gastmaier@gmail.com \
    --cc=jan.sun97@gmail.com \
    --cc=janani.sunil@analog.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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