From: Mark Brown <broonie@kernel.org>
To: Ricard Wanderlof <ricardw@axis.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
alsa-devel <alsa-devel@alsa-project.org>,
Rob Herring <robh+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [RESEND, PATCH v6 1/2] dt-bindings: sound: tlv320adc3xxx: New codec driver
Date: Wed, 1 Dec 2021 15:21:13 +0000 [thread overview]
Message-ID: <YaeS6WqKNRpX2IGs@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2112011603080.30606@lnxricardw1.se.axis.com>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On Wed, Dec 01, 2021 at 04:09:17PM +0100, Ricard Wanderlof wrote:
>
> DT bindings for tlv320adc3xxx driver, currently supporting
> Texas Instruments TLV320ADC3001 and TLV320ADC3101 audio ADCs.
I realise that the threading is broken on all your patch serieses (it
would be good to fix this) but please don't send isolated patches from a
series separately in the middle of pending review for the series, it
just makes things even harder to follow since now there's two different
groups of patches and they're not even grouped by sending date.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Ricard Wanderlof <ricardw@axis.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
alsa-devel <alsa-devel@alsa-project.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [RESEND, PATCH v6 1/2] dt-bindings: sound: tlv320adc3xxx: New codec driver
Date: Wed, 1 Dec 2021 15:21:13 +0000 [thread overview]
Message-ID: <YaeS6WqKNRpX2IGs@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2112011603080.30606@lnxricardw1.se.axis.com>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On Wed, Dec 01, 2021 at 04:09:17PM +0100, Ricard Wanderlof wrote:
>
> DT bindings for tlv320adc3xxx driver, currently supporting
> Texas Instruments TLV320ADC3001 and TLV320ADC3101 audio ADCs.
I realise that the threading is broken on all your patch serieses (it
would be good to fix this) but please don't send isolated patches from a
series separately in the middle of pending review for the series, it
just makes things even harder to follow since now there's two different
groups of patches and they're not even grouped by sending date.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-01 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 15:09 [RESEND, PATCH v6 1/2] dt-bindings: sound: tlv320adc3xxx: New codec driver Ricard Wanderlof
2021-12-01 15:09 ` Ricard Wanderlof
2021-12-01 15:21 ` Mark Brown [this message]
2021-12-01 15:21 ` Mark Brown
2021-12-07 17:35 ` Rob Herring
2021-12-07 17:35 ` Rob Herring
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=YaeS6WqKNRpX2IGs@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=ricardw@axis.com \
--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 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.