From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guillaume Gardet <guillaume.gardet@free.fr>
Cc: peter.ujfalusi@ti.com, alsa-devel@alsa-project.org,
linux-omap@vger.kernel.org, mans.rullgard@linaro.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH V2] Add missing modules aliases to get sound working on omap devices
Date: Thu, 26 Jul 2012 23:00:50 +0100 [thread overview]
Message-ID: <20120726220049.GK4560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FFECC40.5020502@free.fr>
[-- Attachment #1.1: Type: text/plain, Size: 835 bytes --]
On Thu, Jul 12, 2012 at 03:08:16PM +0200, Guillaume Gardet wrote:
> This patch add missing modules aliases to get sound working on omap devices.
So, after a bunch of hand editing I applied this. As I *repeatedly*
requested you should send patches in the format covered in
SubmittingPatches, the main reason it took me so long to get round to
applying this is that I had to strip things like this:
> From 18b1ba8becc3dd256bdaad2d825f46b551debda3 Mon Sep 17 00:00:00 2001
> From: Guillaume GARDET <guillaume.gardet@oliseo.fr>
> Date: Tue, 10 Jul 2012 13:47:16 +0200
> Subject: [PATCH] Add missing modules aliases to fix audio on omap devices
out of the commit message, plus the fact that since you hadn't used an
appropriate subject line for the subsystem your patch didn't turn up
when I searched my mail for patches to be handled.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-07-26 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 13:08 [PATCH V2] Add missing modules aliases to get sound working on omap devices Guillaume Gardet
2012-07-13 10:09 ` Mark Brown
2012-07-17 13:31 ` Guillaume Gardet
2012-07-17 13:37 ` Mark Brown
2012-07-26 22:00 ` 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=20120726220049.GK4560@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=guillaume.gardet@free.fr \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=mans.rullgard@linaro.org \
--cc=peter.ujfalusi@ti.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).