From: David Henningsson <david.henningsson@canonical.com>
To: "Diego Elio Pettenò" <flameeyes@gmail.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: Band-aid solution for Dell Latitude E6410/E6510 microphone
Date: Wed, 29 Sep 2010 08:15:37 +0200 [thread overview]
Message-ID: <4CA2D989.8050205@canonical.com> (raw)
In-Reply-To: <1285726141-26448-1-git-send-email-flameeyes@gmail.com>
On 2010-09-29 04:09, Diego Elio Pettenò wrote:
> Hi all,
>
> I'm sending out a patch that I didn't write (and thus most likely require
> David's Signed-Off), but which I think might be a good idea to at least
> have accessible to search.
>
> As David already pointed out to me, the proper fix for the issue is
> Takashi's commit 75e0eb24ee3ec3549c2e53707dcc87e5f7a2c791, but that hasn't
> made it into .36 RCs and thus seem unlikely to come to users anytime soon.
>
> David's patch is a "band aid" solution; it solves most of the problem by
> adding one more special case to the sigmatel patches; on the other hand it
> makes the internal microphone to work fine on my laptop, which is a good
> thing, right?
It might also break docking station microphones on the same machines,
which is why I thought it was no use trying to send it to stable. But if
stable wants to add it, I'd be glad to give a sign-off or whatever
necessary.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
prev parent reply other threads:[~2010-09-29 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 2:09 Band-aid solution for Dell Latitude E6410/E6510 microphone Diego Elio Pettenò
2010-09-29 2:09 ` [PATCH] ALSA: HDA: Enable internal mic on Dell E6410 and Dell E6510 Diego Elio Pettenò
2010-10-21 15:09 ` Diego Elio Pettenò
2010-10-21 21:28 ` Takashi Iwai
2010-09-29 6:15 ` David Henningsson [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=4CA2D989.8050205@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=flameeyes@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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