From: Conor Dooley <conor@kernel.org>
To: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: dt-bindings: tfa9879: Convert to dtschema
Date: Fri, 22 Sep 2023 19:21:16 +0100 [thread overview]
Message-ID: <20230922-scoreless-battalion-8b33e36066eb@spud> (raw)
In-Reply-To: <c6f795f1-2832-c282-5819-f8f402a312bd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On Fri, Sep 22, 2023 at 10:53:06PM +0530, Bragatheswaran Manickavel wrote:
>
> On 22/09/23 20:56, Conor Dooley wrote:
> > On Fri, Sep 22, 2023 at 12:03:13AM +0530, Bragatheswaran Manickavel wrote:
> > > Convert the tfa9879 audio CODEC bindings to DT schema
> > > No error/warning seen when running make dt_binding_check
> > >
> > > Signed-off-by: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
> > > Changes:
> > > V1 -> V2: Fixed DT syntax errors and doc warning
> > These should be under the --- line, not above it.
> > Perhaps Mark will change it on application.
> > Otherwise,
> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> Thanks for reviewing it.
> Do I need to send a new patch by addressing the above comments ?
To be clear, it's the changelog, not the sign off, that needs to go
under the ---. It'd look like:
Signed-off-by: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
---
Changes:
V1 -> V2: Fixed DT syntax errors and doc warning
Mark often fixes these things when he applies patches, but sending a v2
w/ the changelog fixed might make his life easier.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-22 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 18:33 [PATCH v2] ASoC: dt-bindings: tfa9879: Convert to dtschema Bragatheswaran Manickavel
2023-09-22 15:26 ` Conor Dooley
2023-09-22 17:23 ` Bragatheswaran Manickavel
2023-09-22 18:21 ` Conor Dooley [this message]
2023-09-22 19:28 ` Mark Brown
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=20230922-scoreless-battalion-8b33e36066eb@spud \
--to=conor@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bragathemanick0908@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).