From: Mark Brown <broonie@kernel.org>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Moise Gergaud <moise.gergaud@st.com>,
kernel@stlinux.com, lgirdwood@gmail.com
Subject: Re: [PATCH 0/7] ASoC: sti audio fixes and legacy cleaning
Date: Wed, 26 Oct 2016 11:40:24 +0100 [thread overview]
Message-ID: <20161026104024.GB17252@sirena.org.uk> (raw)
In-Reply-To: <1477320177-30130-1-git-send-email-arnaud.pouliquen@st.com>
[-- Attachment #1.1: Type: text/plain, Size: 450 bytes --]
On Mon, Oct 24, 2016 at 04:42:50PM +0200, Arnaud Pouliquen wrote:
> Audio fixes and cleaning of code associated to stih416 platform.
Please don't mix fixes and cleanups like this, bug fixes ought to get
sent to Linus so they get into the first release they can while cleanups
can wait for the next merge window so you should make sure that any
fixes come at the start of the series in order to ensure that there are
no dependencies on the cleanups.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2016-10-26 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 14:42 [PATCH 0/7] ASoC: sti audio fixes and legacy cleaning Arnaud Pouliquen
2016-10-24 14:42 ` [PATCH 1/7] ASoC: sti: fix errors management Arnaud Pouliquen
2016-10-26 10:46 ` Applied "ASoC: sti: fix errors management" to the asoc tree Mark Brown
2016-10-24 14:42 ` [PATCH 2/7] ASoC: sti: fix channel status update after playback start Arnaud Pouliquen
2016-10-26 10:46 ` Applied "ASoC: sti: fix channel status update after playback start" to the asoc tree Mark Brown
2016-10-24 14:42 ` [PATCH 3/7] ASoC: sti: reset refactoring Arnaud Pouliquen
2016-10-26 10:46 ` Applied "ASoC: sti: reset refactoring" to the asoc tree Mark Brown
2016-10-24 14:42 ` [PATCH 4/7] ASoC: sti: clean unused include Arnaud Pouliquen
2016-10-26 10:46 ` Applied "ASoC: sti: clean unused include" to the asoc tree Mark Brown
2016-10-24 14:42 ` [PATCH 5/7] ASoC: codec: clean legacy in sti-sas Arnaud Pouliquen
2016-10-26 10:46 ` Applied "ASoC: sti-sas: clean legacy in sti-sas" to the asoc tree Mark Brown
2016-10-24 14:42 ` [PATCH 6/7] ASoC: sti: sti-sas: add missing return in messages strings Arnaud Pouliquen
2016-10-26 10:45 ` Applied "ASoC: sti-sas: add missing return in messages strings" to the asoc tree Mark Brown
2016-10-24 14:42 ` [PATCH 7/7] ASoc: codec: sti enable fast io for regmap Arnaud Pouliquen
2016-10-26 10:45 ` Applied "ASoC: sti-sas: enable fast io for regmap" to the asoc tree Mark Brown
2016-10-26 10:40 ` 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=20161026104024.GB17252@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=kernel@stlinux.com \
--cc=lgirdwood@gmail.com \
--cc=moise.gergaud@st.com \
--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