From: Mark Brown <broonie@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] ASoC: tlv320adcx140: Add the tlv320adcx140 codec driver family
Date: Thu, 20 Feb 2020 21:13:07 +0000 [thread overview]
Message-ID: <20200220211307.GM3926@sirena.org.uk> (raw)
In-Reply-To: <5cc47587-eae1-0b41-e91d-f9885a69d75e@ti.com>
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
On Thu, Feb 20, 2020 at 02:52:11PM -0600, Dan Murphy wrote:
> On 2/20/20 2:48 PM, Mark Brown wrote:
> > This doesn't apply against current code, please check and resend.
> Ok this is against linux master should this be against your for-next branch?
Yes, everything except bugfixes should be against the current
development tree (in general things should apply on the tree they're
targetting).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-20 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 12:59 [PATCH v3 0/2] Introduce the TLV320ADCx140 codec family Dan Murphy
2020-02-19 12:59 ` [PATCH v3 1/2] dt-bindings: sound: Add TLV320ADCx140 dt bindings Dan Murphy
2020-02-19 12:59 ` [PATCH v3 2/2] ASoC: tlv320adcx140: Add the tlv320adcx140 codec driver family Dan Murphy
2020-02-20 20:48 ` Mark Brown
2020-02-20 20:52 ` Dan Murphy
2020-02-20 21:13 ` Mark Brown [this message]
2020-02-26 11:18 ` Ricard Wanderlof
2020-02-26 12:43 ` Dan Murphy
2020-02-20 19:24 ` [PATCH v3 0/2] Introduce the TLV320ADCx140 codec family Dan Murphy
2020-02-20 19:44 ` 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=20200220211307.GM3926@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dmurphy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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 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).