From: Mark Brown <broonie@kernel.org>
To: Camel Guo <camelg@axis.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.com,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
kernel@axis.com, dmurphy@ti.com, Camel Guo <camel.guo@axis.com>
Subject: Re: [PATCH v4] ASoC: tlv320adcx140: Add support for configuring GPIO pin
Date: Fri, 18 Sep 2020 12:33:05 +0100 [thread overview]
Message-ID: <20200918113305.GF5703@sirena.org.uk> (raw)
In-Reply-To: <b5cc9041-62ea-d578-db28-c1ab8ec50842@axis.com>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Fri, Sep 18, 2020 at 01:27:50PM +0200, Camel Guo wrote:
> On 9/18/20 1:18 PM, Mark Brown wrote:
> > This needs a DT bindings update for the new property (I thought there
> > was one in prior versions)?
> That patch for DT bindings has no change at all. Now I resent it anyway.
Any patch series you send should be self-contained, if some patches from
a previous version of the series are unchanged you should still resend
them. Picking some patches out of different versions of a series makes
everything less clear and more error prone.
[-- 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: Camel Guo <camelg@axis.com>
Cc: Camel Guo <camel.guo@axis.com>,
lgirdwood@gmail.com, tiwai@suse.com, dmurphy@ti.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
kernel@axis.com
Subject: Re: [PATCH v4] ASoC: tlv320adcx140: Add support for configuring GPIO pin
Date: Fri, 18 Sep 2020 12:33:05 +0100 [thread overview]
Message-ID: <20200918113305.GF5703@sirena.org.uk> (raw)
In-Reply-To: <b5cc9041-62ea-d578-db28-c1ab8ec50842@axis.com>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Fri, Sep 18, 2020 at 01:27:50PM +0200, Camel Guo wrote:
> On 9/18/20 1:18 PM, Mark Brown wrote:
> > This needs a DT bindings update for the new property (I thought there
> > was one in prior versions)?
> That patch for DT bindings has no change at all. Now I resent it anyway.
Any patch series you send should be self-contained, if some patches from
a previous version of the series are unchanged you should still resend
them. Picking some patches out of different versions of a series makes
everything less clear and more error prone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-18 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 7:32 [PATCH v4] ASoC: tlv320adcx140: Add support for configuring GPIO pin Camel Guo
2020-09-18 7:32 ` Camel Guo
2020-09-18 11:18 ` Mark Brown
2020-09-18 11:18 ` Mark Brown
2020-09-18 11:27 ` Camel Guo
2020-09-18 11:27 ` Camel Guo
2020-09-18 11:33 ` Mark Brown [this message]
2020-09-18 11:33 ` 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=20200918113305.GF5703@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=camel.guo@axis.com \
--cc=camelg@axis.com \
--cc=dmurphy@ti.com \
--cc=kernel@axis.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.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 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.