From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: Hungyu Lin <dennylin0707@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: jic23@kernel.org, lars@metafoo.de, Michael.Hennerich@analog.com,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/1] dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding
Date: Sat, 09 May 2026 07:34:17 +0530 [thread overview]
Message-ID: <0D2B5076-A5D7-4D14-B58B-E500585DD465@gmail.com> (raw)
In-Reply-To: <20260508231147.77044-1-dennylin0707@gmail.com>
On 9 May 2026 4:41:46 am IST, Hungyu Lin <dennylin0707@gmail.com> wrote:
>v2:
>- Fix commit message to match binding requirements
>
Hi,
Thank you for the change.
Ideally, multiple logical changes should be split into series. For a single patch you can include changelog like this:
Signed-off-by: ....
---
Changes in v2:
- Fix commit message to match binding requirements
---
.../bindings..
| 94 +++++++++++++++++++
If reviewer specifically asked to update commit message, you can mention in the changelog as well. for examle:
- Fix commit message based on input from <Reviewer Name>
Replace <Reviewer Name> with the actual reviewer.
>Hungyu Lin (1):
> dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding
>
> .../bindings/iio/adc/adi,ad7816.yaml | 94 +++++++++++++++++++
> 1 file changed, 94 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7816.yaml
>
prev parent reply other threads:[~2026-05-09 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 23:11 [PATCH v2 0/1] dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding Hungyu Lin
2026-05-08 23:11 ` [PATCH v2 1/1] " Hungyu Lin
2026-05-09 2:04 ` Sanjay Chitroda [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=0D2B5076-A5D7-4D14-B58B-E500585DD465@gmail.com \
--to=sanjayembeddedse@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dennylin0707@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@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