From: Rob Herring <robh@kernel.org>
To: "Xu, Yang" <raphael-xu@ti.com>
Cc: Raphael-Xu <13691752556@139.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Ding, Shenghao" <shenghao-ding@ti.com>,
"Navada Kanyana, Mukund" <navada@ti.com>,
"Syrus, Andy" <asyrus@ti.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH v5] update tas2780.yaml
Date: Wed, 20 Jul 2022 17:02:53 -0600 [thread overview]
Message-ID: <CAL_JsqK6GPC0gUFePef4SuCR0KiuFi3L21DpMAp4=6EUeDub6A@mail.gmail.com> (raw)
In-Reply-To: <782171baf71849cc8c23177555ee2f7d@ti.com>
On Tue, Jul 19, 2022 at 11:44 PM Xu, Yang <raphael-xu@ti.com> wrote:
>
> Hi Rob,
>
> One more question of tas27xx.yaml.Would you like us to delete tas27xx.yaml and submit new tas2764.yaml in updated format,or we just revert to old version tas2764.yaml commit?
> Thanks.
I think tas2770.yaml and tas2780.yaml should both be removed with
ti,tas2770 compatible added to tas27xx.yaml.
>
> Regards
> Raphael
>
> -----Original Message-----
> From: Xu, Yang <>
> Sent: Wednesday, July 20, 2022 11:48 AM
> To: 'Rob Herring' <robh@kernel.org>; Raphael-Xu <13691752556@139.com>
> Cc: alsa-devel@alsa-project.org; Ding, Shenghao <shenghao-ding@ti.com>; Navada Kanyana, Mukund <navada@ti.com>; Syrus, Andy <asyrus@ti.com>; broonie@kernel.org; devicetree@vger.kernel.org
> Subject: RE: [EXTERNAL] Re: [PATCH v5] update tas2780.yaml
>
> Hi Rob,
>
> Please see my reply.
>
> -----Original Message-----
> From: Rob Herring <robh@kernel.org>
> Sent: Wednesday, July 13, 2022 10:52 PM
> To: Raphael-Xu <13691752556@139.com>
> Cc: alsa-devel@alsa-project.org; Xu, Yang <raphael-xu@ti.com>; Ding, Shenghao <shenghao-ding@ti.com>; Navada Kanyana, Mukund <navada@ti.com>; Syrus, Andy <asyrus@ti.com>; broonie@kernel.org; devicetree@vger.kernel.org
> Subject: [EXTERNAL] Re: [PATCH v5] update tas2780.yaml
>
> On Tue, Jul 12, 2022 at 01:08:57PM +0800, Raphael-Xu wrote:
> > 1.remove unused item in DT 2.revise the format
>
> Again, fix your subject. Run 'git log --oneline Documentation/devicetree/bindings/sound/' for inspiration of the format of the subject.
> [RX]:just submit new patch
Closer, but still the wrong subject. You are missing spaces.
> However, there's a bigger issue here. We already have a binding for this device. It's in tas27xx.yaml. And you added 2780 to it, so why did you add another schema? (All the same issues in that patch too. wrong subject, broken schema. So you haven't learned.) [RX]:We will follow tas2780 patch format and submit separate patch if you think tas2780 patch is acceptable.
> And then there is also tas2770.yaml which appears to be about the same as well.
> [RX]:We will follow tas2780 patch format and submit separate patch if you think tas2780 patch is acceptable.
Is deleting tas2780.yaml and just adding ti,tas2780 compatible not
sufficient? Why fix tas2780.yaml and then delete it? Doing the same
for tas2770 can be separate.
Rob
> >
> > Signed-off-by: Raphael-Xu <13691752556@139.com>
> > ---
> > .../devicetree/bindings/sound/tas2780.yaml | 19 +++++++++++--------
> > 1 file changed, 11 insertions(+), 8 deletions(-)
prev parent reply other threads:[~2022-07-20 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 5:08 [PATCH v5] update tas2780.yaml Raphael-Xu
2022-07-13 14:51 ` Rob Herring
2022-07-20 3:48 ` [EXTERNAL] " Xu, Yang
2022-07-20 5:43 ` Xu, Yang
2022-07-20 23:02 ` Rob Herring [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='CAL_JsqK6GPC0gUFePef4SuCR0KiuFi3L21DpMAp4=6EUeDub6A@mail.gmail.com' \
--to=robh@kernel.org \
--cc=13691752556@139.com \
--cc=alsa-devel@alsa-project.org \
--cc=asyrus@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=navada@ti.com \
--cc=raphael-xu@ti.com \
--cc=shenghao-ding@ti.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 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).