Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Michael Schwingen <michael@schwingen.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: PATCH: Maxdata Favorit 100XS support
Date: Tue, 24 Feb 2009 12:35:02 +0100	[thread overview]
Message-ID: <s5hbpss83vd.wl%tiwai@suse.de> (raw)
In-Reply-To: <20090222175845.GA30047@discworld.dascon.de>

At Sun, 22 Feb 2009 18:58:45 +0100,
Michael Schwingen wrote:
> 
> On Thu, Feb 05, 2009 at 08:28:50AM +0100, Takashi Iwai wrote:
> > The patch looks almost good but there are a few issues to fix.
> > 
> > First off, please use a unified diff (diff -u) for a patch.
> > Then, rebase your patch to the latest sound git tree[*] or 2.6.29-rc3 
> > at least.
> >    git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
> > 
> > Some stuff in patch_realtek.c in the latest tree was changed to be
> > incompatible from 2.6.28.  For example,
> > 
> > > + 	[ALC260_FAVORIT100] = {
> > > + 		.mixers = { alc260_favorit100_mixer,
> > > + 			    alc260_capture_mixer },
> > 
> > The capture mixer is now created dynamically.  Usually you don't need
> > pass capture_mixer array here.
> > 
> > > + 		.init_verbs = { alc260_acer_init_verbs },
> > 
> > Don't you use alc260_favorit100_init_verbs?
> > 
> > 
> > Could you fix these and repost?
> 
> Here is the updated patch, against the git version - is the diff format OK
> now?

Yes, it was merged to sound tree.  Sorry, forgot to notify you.

Thanks!

Takashi

      parent reply	other threads:[~2009-02-24 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 19:30 PATCH: Maxdata Favorit 100XS support Michael Schwingen
2009-02-05  7:28 ` Takashi Iwai
2009-02-05  8:36   ` Michael Schwingen
     [not found]   ` <20090222175845.GA30047@discworld.dascon.de>
2009-02-24 11:35     ` Takashi Iwai [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=s5hbpss83vd.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=michael@schwingen.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