From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
kernel-janitors@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] ASoC: constify snd_soc_ops structures
Date: Tue, 25 Oct 2016 15:08:52 +0100 [thread overview]
Message-ID: <20161025140852.GV17252@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1610250754220.2084@hadrien>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On Tue, Oct 25, 2016 at 07:55:00AM +0200, Julia Lawall wrote:
> On Mon, 24 Oct 2016, Mark Brown wrote:
> > You split out a few drivers as separate patches but not these ones -
> > what's special about these ones?
> If it's preferred, I could send them all one file at a time, or when the
> maintainers are very similar just send one patch to all the maintainers.
For something like this it doesn't matter so much, it was mainly just
the consistency that was bothering me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-10-25 14:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 14:55 [PATCH 0/7] constify snd_soc_ops structures Julia Lawall
2016-10-15 14:55 ` [PATCH 1/7] ASoC: intel: broadwell: " Julia Lawall
2016-10-17 2:22 ` [alsa-devel] " Keyon Jie
2016-10-24 18:01 ` Applied "ASoC: intel: broadwell: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-15 14:55 ` [PATCH 2/7] ASoC: atmel_wm8904: constify snd_soc_ops structures Julia Lawall
2016-10-18 8:13 ` Nicolas Ferre
2016-10-24 18:01 ` Applied "ASoC: atmel_wm8904: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-15 14:55 ` [PATCH 3/7] ASoC: rockchip: constify snd_soc_ops structures Julia Lawall
2016-10-24 18:01 ` Applied "ASoC: rockchip: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-15 14:55 ` [PATCH 4/7] ASoC: qcom: storm: constify snd_soc_ops structures Julia Lawall
2016-10-24 18:01 ` Applied "ASoC: qcom: storm: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-15 14:55 ` [PATCH 5/7] ASoC: constify snd_soc_ops structures Julia Lawall
2016-10-24 17:34 ` Mark Brown
2016-10-24 19:48 ` Julia Lawall
2016-10-25 5:55 ` Julia Lawall
2016-10-25 8:04 ` Joe Perches
2016-10-25 8:39 ` Julia Lawall
2016-10-25 14:08 ` Mark Brown [this message]
2016-10-15 14:55 ` [PATCH 6/7] " Julia Lawall
2016-10-24 18:01 ` Applied "ASoC: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-15 14:55 ` [PATCH 7/7] ASoC: tegra: constify snd_soc_ops structures Julia Lawall
2016-10-24 18:01 ` Applied "ASoC: tegra: constify snd_soc_ops structures" to the asoc tree 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=20161025140852.GV17252@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--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