From: Stephan Gerhold <stephan@gerhold.net> To: Alexander Martinz <amartinz@shiftphones.com> Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org, Dylan Van Assche <me@dylanvanassche.be>, linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>, Liam Girdwood <lgirdwood@gmail.com>, Rob Herring <robh+dt@kernel.org>, Caleb Connolly <caleb@connolly.tech>, Mark Brown <broonie@kernel.org>, ~postmarketos/upstreaming@lists.sr.ht, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, phone-devel@vger.kernel.org Subject: Re: [PATCH 2/2] ASoC: dt-bindings: nxp,tfa989x: Add tfa9890 support Date: Fri, 3 Jun 2022 20:06:39 +0200 [thread overview] Message-ID: <YppNaL5r5EN3SUsU@gerhold.net> (raw) In-Reply-To: <20220602164504.261361-2-amartinz@shiftphones.com> On Thu, Jun 02, 2022 at 06:45:04PM +0200, Alexander Martinz wrote: > Document TFA9890 binding for tfa989x. > > Signed-off-by: Alexander Martinz <amartinz@shiftphones.com> The dt-bindings patch should usually come first in the patch series. Anyway, no need to resend just for that IMO: Reviewed-by: Stephan Gerhold <stephan@gerhold.net> > --- > Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml b/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml > index b9b1dba40856..7f2e68ff6d34 100644 > --- a/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml > +++ b/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml > @@ -15,6 +15,7 @@ allOf: > properties: > compatible: > enum: > + - nxp,tfa9890 > - nxp,tfa9895 > - nxp,tfa9897 > > -- > 2.36.1 >
WARNING: multiple messages have this Message-ID (diff)
From: Stephan Gerhold <stephan@gerhold.net> To: Alexander Martinz <amartinz@shiftphones.com> Cc: ~postmarketos/upstreaming@lists.sr.ht, phone-devel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>, alsa-devel@alsa-project.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Caleb Connolly <caleb@connolly.tech>, Dylan Van Assche <me@dylanvanassche.be> Subject: Re: [PATCH 2/2] ASoC: dt-bindings: nxp,tfa989x: Add tfa9890 support Date: Fri, 3 Jun 2022 20:06:39 +0200 [thread overview] Message-ID: <YppNaL5r5EN3SUsU@gerhold.net> (raw) In-Reply-To: <20220602164504.261361-2-amartinz@shiftphones.com> On Thu, Jun 02, 2022 at 06:45:04PM +0200, Alexander Martinz wrote: > Document TFA9890 binding for tfa989x. > > Signed-off-by: Alexander Martinz <amartinz@shiftphones.com> The dt-bindings patch should usually come first in the patch series. Anyway, no need to resend just for that IMO: Reviewed-by: Stephan Gerhold <stephan@gerhold.net> > --- > Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml b/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml > index b9b1dba40856..7f2e68ff6d34 100644 > --- a/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml > +++ b/Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml > @@ -15,6 +15,7 @@ allOf: > properties: > compatible: > enum: > + - nxp,tfa9890 > - nxp,tfa9895 > - nxp,tfa9897 > > -- > 2.36.1 >
next prev parent reply other threads:[~2022-06-03 18:08 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-02 16:45 [PATCH 1/2] ASoC: codecs: tfa989x: Add support for tfa9890 Alexander Martinz 2022-06-02 16:45 ` Alexander Martinz 2022-06-02 16:45 ` [PATCH 2/2] ASoC: dt-bindings: nxp,tfa989x: Add tfa9890 support Alexander Martinz 2022-06-02 16:45 ` Alexander Martinz 2022-06-03 18:06 ` Stephan Gerhold [this message] 2022-06-03 18:06 ` Stephan Gerhold 2022-06-05 22:44 ` Rob Herring 2022-06-05 22:44 ` Rob Herring 2022-06-03 18:20 ` [PATCH 1/2] ASoC: codecs: tfa989x: Add support for tfa9890 Stephan Gerhold 2022-06-03 18:20 ` Stephan Gerhold 2022-06-07 10:45 ` Mark Brown 2022-06-07 10:45 ` 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=YppNaL5r5EN3SUsU@gerhold.net \ --to=stephan@gerhold.net \ --cc=alsa-devel@alsa-project.org \ --cc=amartinz@shiftphones.com \ --cc=broonie@kernel.org \ --cc=caleb@connolly.tech \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=lgirdwood@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=me@dylanvanassche.be \ --cc=phone-devel@vger.kernel.org \ --cc=robh+dt@kernel.org \ --cc=tiwai@suse.com \ --cc=~postmarketos/upstreaming@lists.sr.ht \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.