From: Lee Revell <rlrevell@joe-job.com>
To: Andrew Morton <akpm@osdl.org>
Cc: alsa-devel@lists.sourceforge.net,
Norbert Preining <preining@logic.at>,
linux-kernel@vger.kernel.org
Subject: Re: alsa 1.0.11, 2.6.17-rc6-mm2, kernel BUG
Date: Sat, 17 Jun 2006 13:26:46 -0400 [thread overview]
Message-ID: <1150565207.26252.69.camel@mindpipe> (raw)
In-Reply-To: <20060617100738.cd40f0bf.akpm@osdl.org>
On Sat, 2006-06-17 at 10:07 -0700, Andrew Morton wrote:
> Judging from the response: no.
>
> If you would, please keep a close eye on -mm's over the next few
> weeks, let
> us know if/when this bug propagates into -mm. Thanks.
>
My hunch it that it's more likely an upstream -mm bug than an ALSA
issue.
Lee
WARNING: multiple messages have this Message-ID (diff)
From: Lee Revell <rlrevell@joe-job.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Norbert Preining <preining@logic.at>,
alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Alsa-devel] alsa 1.0.11, 2.6.17-rc6-mm2, kernel BUG
Date: Sat, 17 Jun 2006 13:26:46 -0400 [thread overview]
Message-ID: <1150565207.26252.69.camel@mindpipe> (raw)
In-Reply-To: <20060617100738.cd40f0bf.akpm@osdl.org>
On Sat, 2006-06-17 at 10:07 -0700, Andrew Morton wrote:
> Judging from the response: no.
>
> If you would, please keep a close eye on -mm's over the next few
> weeks, let
> us know if/when this bug propagates into -mm. Thanks.
>
My hunch it that it's more likely an upstream -mm bug than an ALSA
issue.
Lee
next prev parent reply other threads:[~2006-06-17 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 21:05 alsa 1.0.11, 2.6.17-rc6-mm2, kernel BUG Norbert Preining
2006-06-17 17:07 ` Andrew Morton
2006-06-17 17:07 ` Andrew Morton
2006-06-17 17:26 ` Lee Revell [this message]
2006-06-17 17:26 ` [Alsa-devel] " Lee Revell
2006-06-18 17:39 ` Norbert Preining
2006-06-18 17:39 ` Norbert Preining
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=1150565207.26252.69.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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.