alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Leon Romanovsky <leon@leon.nu>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"patch@alsa-project.org" <patch@alsa-project.org>,
	Stephen Warren <swarren@nvidia.com>,
	Paul Fertser <fercerpav@gmail.com>,
	Marc Dietrich <marvin24@gmx.de>, Oliver Grawert <ogra@ubuntu.com>,
	Andrey Danin <danindrey@mail.ru>
Subject: Re: [PATCH] Add default config for tegra-alc5632 (as found on paz00)
Date: Tue, 7 Feb 2012 11:26:16 +0000	[thread overview]
Message-ID: <20120207112616.GD3332@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CALq1K=+brR4OgPzfANKTFDoD-8Pbm0WjwXH+ZzShHvkGg6ntwA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 450 bytes --]

On Tue, Feb 07, 2012 at 08:57:59AM +0200, Leon Romanovsky wrote:

> I want to raise our old question: "How do we need to call this card ?
> Do we need to call it tegra-alc5632, as was in pre-DT era ? Or do we
> need to call it "Compal PAZ00" as we introduced in DT patches ?".

> The both names are applicable because "Compal PAZ00" is the name of
> notebook (hardware board) and tegra-alc5632 is the name of chips were
> used.

I really don't care.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-02-07 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 20:51 [PATCH] Add default config for tegra-alc5632 (as found on paz00) Paul Fertser
2012-02-07  5:52 ` Stephen Warren
2012-02-07  6:57   ` Leon Romanovsky
2012-02-07 11:26     ` Mark Brown [this message]
2012-02-07 12:54     ` Paul Fertser
2012-02-07 13:13       ` Mark Brown
2012-02-24  8:43         ` Paul Fertser
2012-02-27 16:32           ` Takashi Iwai
2012-02-07 11:45 ` 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=20120207112616.GD3332@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=danindrey@mail.ru \
    --cc=fercerpav@gmail.com \
    --cc=leon@leon.nu \
    --cc=marvin24@gmx.de \
    --cc=ogra@ubuntu.com \
    --cc=patch@alsa-project.org \
    --cc=swarren@nvidia.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).