mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Jaroslav Kysela <perex@suse.cz>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [ALSA PATCH] HG repo sync
Date: Thu, 29 Jun 2006 12:40:56 +0200	[thread overview]
Message-ID: <s5h4py4p7lz.wl%tiwai@suse.de> (raw)
In-Reply-To: <20060629025306.455c89ce.akpm@osdl.org>

At Thu, 29 Jun 2006 02:53:06 -0700,
Andrew Morton wrote:
> 
> On Thu, 29 Jun 2006 11:39:35 +0200 (CEST)
> Jaroslav Kysela <perex@suse.cz> wrote:
> 
> > Linus, please do an update from:
> > 
> >   http://www.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git
> >
> 
> As far as I can tell none of this has had any testing in -mm.

Hmm, it's the result of infrequent update of alsa git tree...

>  The tree I
> get from
> git+ssh://master.kernel.org/pub/scm/linux/kernel/git/perex/alsa-current.git
> has quite different changes in it.

Yes, alsa-current git contains more changes currently in ALSA HG
repo.  alsa git contains only (safe and important) changes for
upstream.

> What can we do about this?

In this patchset, the biggest patch is the addition of echoaudio
driver.
It's OK to postpone this for 2.6.19.  But this driver has been tested
over three years although unfortunately it didn't land to mm by
mistake (we forgot to move the code after 2.6.17 feature freeze).

Another relatively big patch is the fix for realtek codecs.  This is
no intrusive patch but addition of the support of more new devices.
It should get in, if we want to reduce the future bugzilla entries :)

The rest are obvious fixes, picked up from LKML and alsa-devel.  They
need to be merged anyway sooner or later.


Takashi

  reply	other threads:[~2006-06-29 10:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29  9:39 Jaroslav Kysela
2006-06-29  9:53 ` Andrew Morton
2006-06-29 10:40   ` Takashi Iwai [this message]
2006-06-29 10:48     ` Jaroslav Kysela
2006-06-29 10:56     ` Andrew Morton

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=s5h4py4p7lz.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®