From: Randy Dunlap <randy.dunlap@oracle.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Peer Chen" <pchen@nvidia.com>,
<alsa-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, Andy Currid <ACurrid@nvidia.com>,
Brian Lazara <BLazara@nvidia.com>,
jgarzik@pobox.com, Emily Jiang <ejiang@nvidia.com>
Subject: Re: [Alsa-devel] [Patch] Audio: Add nvidia HD Audio controllers of MCP67 support to hda_intel.c
Date: Tue, 31 Oct 2006 07:43:45 -0800 [thread overview]
Message-ID: <20061031074345.18d57e88.randy.dunlap@oracle.com> (raw)
In-Reply-To: <s5hr6wotukx.wl%tiwai@suse.de>
On Tue, 31 Oct 2006 15:42:54 +0100 Takashi Iwai wrote:
> At Tue, 31 Oct 2006 15:33:58 +0800,
> Peer Chen wrote:
> >
> > Add the support for HD audio controllers of MCP51,MCP55,MCP61,MCP65 & MCP67.
> > The following hda_intel.c patch is based on kernel 2.6.18.
> >
> > Signed-off by: Peer Chen <pchen@nvidia.com>
>
> Applied to ALSA tree. But I didn't add it to push-to-2.6.19-tree
> because apparently no one has tested the patch well yet.
>
> (BTW, your patch attached there was broken, so I had to apply it
> manually. At the next time, please either inline the patch in a text
> mail, or attach a plain text patch if inlining is not possible with
> your MUA/MTA.)
Patches should also be sent made to apply to a current kernel
tree, like 2.6.19-rc3, 2.6.19-rc4, 2.6.19-rc3-git8,
Linus's git tree, or Andrew's -mm tree if that is the only
place where the patch fits, or even to a subsystem tree (e.g., ALSA).
---
~Randy
next prev parent reply other threads:[~2006-10-31 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15F501D1A78BD343BE8F4D8DB854566B0C42D52B@hkemmail01.nvidia.com>
2006-10-31 14:42 ` Takashi Iwai
2006-10-31 15:43 ` Randy Dunlap [this message]
2006-10-31 16:01 ` Takashi Iwai
2006-10-31 16:00 ` Randy Dunlap
2006-11-17 8:46 ` Peer Chen
2006-11-17 10:52 ` Takashi Iwai
2006-11-20 2:02 ` Peer Chen
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=20061031074345.18d57e88.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=ACurrid@nvidia.com \
--cc=BLazara@nvidia.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ejiang@nvidia.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pchen@nvidia.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
Powered by JetHome