From: Mark Brown <broonie@kernel.org>
To: Kenneth Westfield <kwestfie@codeaurora.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Kumar Gala <galak@codeaurora.org>,
Banajit Goswami <bgoswami@codeaurora.org>,
Patrick Lai <plai@codeaurora.org>, Takashi Iwai <tiwai@suse.de>,
Jaroslav Kysela <perex@perex.cz>,
David Brown <davidb@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>,
ALSA Mailing List <alsa-devel@alsa-project.org>,
MSM Mailing List <linux-arm-msm@vger.kernel.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V8 4/5] ASoC: Allow for building QCOM drivers
Date: Mon, 16 Mar 2015 11:25:10 +0000 [thread overview]
Message-ID: <20150316112510.GL28806@sirena.org.uk> (raw)
In-Reply-To: <1426233668-30593-5-git-send-email-kwestfie@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
On Fri, Mar 13, 2015 at 01:01:07AM -0700, Kenneth Westfield wrote:
> From: Kenneth Westfield <kwestfie@codeaurora.org>
>
> Allow for the Qualcomm Technologies ASoC drivers
> to build.
Applied everything up to here, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-03-16 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 8:01 [PATCH V8 0/5] ASoC: QCOM: Add support for ipq806x SOC Kenneth Westfield
2015-03-13 8:01 ` [PATCH V8 1/5] ASoC: qcom: Document Storm bindings Kenneth Westfield
2015-03-13 8:01 ` [PATCH V8 2/5] ASoC: qcom: Add Storm machine driver Kenneth Westfield
2015-03-13 8:01 ` [PATCH V8 3/5] ASoC: qcom: Add ability to build QCOM drivers Kenneth Westfield
2015-03-13 8:01 ` [PATCH V8 4/5] ASoC: Allow for building " Kenneth Westfield
2015-03-16 11:25 ` Mark Brown [this message]
2015-03-13 8:01 ` [PATCH V8 5/5] ARM: dts: Model IPQ LPASS audio hardware Kenneth Westfield
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=20150316112510.GL28806@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=kwestfie@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=plai@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®