From: Mark Brown <broonie@kernel.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "Lior Amsalem" <alior@marvell.com>,
"Brian Austin" <brian.austin@cirrus.com>,
=?iso-8859-1?B?LmNvbT4=?=@alsa-project.org,
alsa-devel@alsa-project.org,
"Liam Girdwood" <liam.r.girdwood@linux.intel.com>,
=?iso-8859-1?Q?Cl=E9ment_=3Cgregory=2Eclement=40free-electrons?=@alsa-project.org,
Gregory@alsa-project.org,
"Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>
Subject: Re: Regression caused by "ASoC: core: Rework SOC_DOUBLE_R_SX_TLV add SOC_SINGLE_SX_TLV"
Date: Wed, 19 Mar 2014 16:50:50 +0000 [thread overview]
Message-ID: <20140319165050.GR11706@sirena.org.uk> (raw)
In-Reply-To: <20140319174602.667f04ba@skate>
[-- Attachment #1.1: Type: text/plain, Size: 193 bytes --]
On Wed, Mar 19, 2014 at 05:46:02PM +0100, Thomas Petazzoni wrote:
> Can you ensure to Cc: stable@ to get the patch included in the
> appropriate previous kernel releases?
I did that already.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-03-19 16:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 13:48 Regression caused by "ASoC: core: Rework SOC_DOUBLE_R_SX_TLV add SOC_SINGLE_SX_TLV" Thomas Petazzoni
2014-01-30 14:59 ` Brian Austin
2014-01-30 15:05 ` Thomas Petazzoni
2014-01-30 15:23 ` Brian Austin
2014-01-30 15:37 ` Brian Austin
2014-01-30 16:56 ` Thomas Petazzoni
2014-01-30 17:13 ` Brian Austin
2014-01-30 17:16 ` Thomas Petazzoni
2014-01-30 17:23 ` Brian Austin
2014-02-10 14:22 ` Thomas Petazzoni
2014-02-14 20:17 ` Mark Brown
2014-02-17 13:14 ` Thomas Petazzoni
2014-02-17 14:59 ` Michael Trimarchi
2014-02-17 15:03 ` Michael Trimarchi
2014-02-17 15:16 ` Thomas Petazzoni
2014-03-19 15:31 ` Brian Austin
2014-03-19 16:46 ` Thomas Petazzoni
2014-03-19 16:50 ` Mark Brown [this message]
2014-03-19 17:45 ` Thomas Petazzoni
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=20140319165050.GR11706@sirena.org.uk \
--to=broonie@kernel.org \
--cc==?iso-8859-1?B?LmNvbT4=?=@alsa-project.org \
--cc==?iso-8859-1?Q?Cl=E9ment_=3Cgregory=2Eclement=40free-electrons?=@alsa-project.org \
--cc=Gregory@alsa-project.org \
--cc=alior@marvell.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=thomas.petazzoni@free-electrons.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