From: Takashi Iwai <tiwai@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: Lee Revell <rlrevell@joe-job.com>, Andrew Morton <akpm@osdl.org>,
Jaroslav Kysela <perex@suse.cz>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [ALSA PATCH] 1.0.9b+
Date: Fri, 29 Jul 2005 11:46:47 +0200 [thread overview]
Message-ID: <s5hack6c5bs.wl%tiwai@suse.de> (raw)
In-Reply-To: <20050728210738.GC2231@redhat.com>
At Thu, 28 Jul 2005 17:07:38 -0400,
Dave Jones wrote:
>
> On Thu, Jul 28, 2005 at 03:06:02PM -0400, Lee Revell wrote:
>
> > > The git-alsa.patch in -mm which I obtain from
> > > master.kernel.org:/pub/scm/linux/kernel/git/perex/alsa-current.git is
> > > empty. So we're now wanting to merge 4,000 lines of unreviewed code which
> > > hasn't been tested in -mm at approximately the -rc4 stage.
> >
> > Lots of people install ALSA independently from the kernel (like all the
> > audio oriented distro users), probably a lot more than run -mm, so it's
> > not completely unreviewed.
>
> There's a big difference between 'unreviewed' and 'untested'.
> With drivers that support n variants of a piece of hardware,
> hearing back that a driver works fine from someone isn't really
> worth anything if the changes break for all the other users
> of that driver that have a different variant, which haven't tested it yet.
>
> We have a testing/review process in place, attempts to short-circuit
> it should be prevented. Especially from a subsystem that
> historically has had a number of issues wrt regressions each release.
Oh, I missed your talk in OLS ;)
Basically I agree with the argument above. Some hardware-specific
regressions are very hard to find only from review. The famous
problem with ThinkPad in the last update was such a kind. More tests
in a bigger place like mm tree would be required, indeed.
Unfortunately, the sync between ALSA and mm tree didn't work well
because of troubles with git/cogito at this time. The sync process
shall be improved from now on. So, please consider this as an
exception.
Takashi
next prev parent reply other threads:[~2005-07-29 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 13:57 [ALSA PATCH] 1.0.9b+ Jaroslav Kysela
2005-07-28 17:25 ` Andrew Morton
2005-07-28 19:06 ` Lee Revell
2005-07-28 19:13 ` Andrew Morton
2005-07-28 21:07 ` Dave Jones
2005-07-29 9:46 ` Takashi Iwai [this message]
2005-07-28 22:34 ` Alistair John Strachan
2005-07-29 2:07 ` Andrew Morton
2005-07-29 7:39 ` Jaroslav Kysela
2005-07-30 13:42 ` Daniel Egger
2005-08-01 8:58 ` Takashi Iwai
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=s5hack6c5bs.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.