From: Mark Brown <broonie@kernel.org>
To: Simran Rai <ssimran@broadcom.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Lori Hikichi <lhikichi@broadcom.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org,
Arun Parameswaran <arunp@broadcom.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v3 0/3] sound: soc: Add audio support for Broadcom Cygnus SoC
Date: Sat, 7 Nov 2015 09:18:37 +0000 [thread overview]
Message-ID: <20151107091837.GA6746@sirena.org.uk> (raw)
In-Reply-To: <1446862965-18667-1-git-send-email-ssimran@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
On Fri, Nov 06, 2015 at 06:22:42PM -0800, Simran Rai wrote:
> Simran Rai (3):
> dt-bindings: sound: Add DT bindings for Broadcom Cygnus audio
> sound: soc: Add Cygnus audio DAI driver
> sound: soc: Add Cygnus audio DMA driver
To repeat what I said last time:
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identify relevant patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-11-07 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 2:22 [PATCH v3 0/3] sound: soc: Add audio support for Broadcom Cygnus SoC Simran Rai
2015-11-07 2:22 ` [PATCH v3 1/3] dt-bindings: sound: Add DT bindings for Broadcom Cygnus audio Simran Rai
2015-11-09 16:32 ` Rob Herring
2015-11-07 2:22 ` [PATCH v3 2/3] sound: soc: Add Cygnus audio DAI driver Simran Rai
2015-11-07 2:22 ` [PATCH v3 3/3] sound: soc: Add Cygnus audio DMA driver Simran Rai
2015-11-07 9:18 ` Mark Brown [this message]
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=20151107091837.GA6746@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=arunp@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=lhikichi@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=ssimran@broadcom.com \
--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).