public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Andrew Morton <akpm@osdl.org>
Cc: Greg Stark <gsstark@mit.edu>,
	s0348365@sms.ed.ac.uk, linux-kernel@vger.kernel.org,
	pmcfarland@downeast.net
Subject: Re: OSS Audio borked between 2.6.6 and 2.6.10
Date: 21 Mar 2005 23:16:53 -0500	[thread overview]
Message-ID: <87is3kco22.fsf@stark.xeocode.com> (raw)
In-Reply-To: <20050321163859.71429a92.akpm@osdl.org>


Andrew Morton <akpm@osdl.org> writes:

> Greg Stark <gsstark@mit.edu> wrote:
> >
> > Andrew Morton <akpm@osdl.org> writes:
> > 
> > > Herbert tells me that this might be fixed in 2.6.11.  Did you try that?
> > 
> > Nope. I'll try that. 
> 
> Did it work?

Oops, sorry I didn't get back. 
Yes. It works fine in 2.6.11.3
Thanks a lot for the help.

-- 
greg


  reply	other threads:[~2005-03-22  4:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12 18:31 OSS Audio borked between 2.6.6 and 2.6.10 Greg Stark
2005-03-13  6:52 ` Patrick McFarland
2005-03-13 22:26   ` Greg Stark
2005-03-14  0:48     ` Martin Schlemmer
2005-03-14  1:03     ` Alistair John Strachan
2005-03-14  3:50       ` Greg Stark
2005-03-14  4:07         ` Andrew Morton
2005-03-14  4:42           ` Greg Stark
2005-03-14  4:55             ` Andrew Morton
2005-03-14  5:39             ` Greg Stark
2005-03-14  5:57               ` Andrew Morton
2005-03-14  6:21                 ` Greg Stark
2005-03-14  6:48                   ` Andrew Morton
2005-03-14  8:59               ` Greg Stark
2005-03-14  9:53                 ` Andrew Morton
2005-03-14 15:40                   ` Greg Stark
2005-03-14 15:52                     ` John W. Linville
2005-03-22  0:38                     ` Andrew Morton
2005-03-22  4:16                       ` Greg Stark [this message]
2005-03-14 15:33                 ` John W. Linville

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=87is3kco22.fsf@stark.xeocode.com \
    --to=gsstark@mit.edu \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmcfarland@downeast.net \
    --cc=s0348365@sms.ed.ac.uk \
    /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