linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ryan C. Bonham" <Ryan@srfarms.com>
To: Linus Torvalds <torvalds@transmeta.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: RE: Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up
Date: Mon, 13 Aug 2001 14:53:34 -0400	[thread overview]
Message-ID: <19AB8F9FA07FB0409732402B4817D75A038A5F@FILESERVER.SRF.srfarms.com> (raw)

Hi,

Ok I am going to stick my two cents in here.. I am not a Linux programmer,
and I am not going to pretend I am, but I do use Linux, have for quite some
time.. I am also implementing Linux in a business.. At home I use custom
built kernels, and play with experimental drivers, etc.. I patch/compile new
kernels all the time. I am running 2.4.8 at my house..(I have a sound
blaster live, and haven't had any problems with that...(all this is besides
the point)..

Anyways,  more to the point.. I don't see the problem with linus putting the
new driver in the 2.4.8 kernel.. Users who are compiling their own kernels,
know that a broken driver is a risk with any kernel.. And for the rest of
the users that rely on Redhat or another Dist company to provide kernels,
are fine, because I know Redhat won't package 2.4.8 with a broken sound
driver like that.. They will either fix (patch) it, or use 2.4.7.. As far as
this being a stable kernel release.. Ok that's true, so why not put it in
the AC tree and work out the bugs with there instead of Linus kernel..

So my basic question is; Alan, can you leave the new sound driver in your AC
kernels? Your kernels are great, and I would love to run them with the new
driver, even if it means I have to find some problems... 

Ok i am done putting my two cents in where it is't wanted :)

Ryan

> -----Original Message-----
> From: Linus Torvalds [mailto:torvalds@transmeta.com]
> Sent: Sunday, August 12, 2001 6:10 PM
> To: Alan Cox
> Cc: Manuel McLure; linux-kernel@vger.kernel.org
> Subject: Re: Hang problem on Tyan K7 Thunder resolved -- SB Live!
> heads-up
> 
> 
> 
> On Sun, 12 Aug 2001, Alan Cox wrote:
> >
> > so I think Linus should do the only sane thing - back it 
> out. I'm backing
> > it out of -ac. Of my three boxes, one spews noise, one 
> locks up smp and
> > one works.
> 
> The problem with backing it out is that apparently nobody has tried to
> really maintain it for a year, and if it gets backed out 
> nobody will even
> bother to try to fix it. So I'll let it be for a while, at least.
> 
> 		Linus
> 
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

             reply	other threads:[~2001-08-13 18:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 18:53 Ryan C. Bonham [this message]
2001-08-13 18:58 ` Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up Daniel T. Chen
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13 19:11 Ryan C. Bonham
2001-08-13 18:54 Anton Altaparmakov
     [not found] <no.id>
2001-08-12 22:30 ` Alan Cox
2001-08-13 12:16 ` Alan Cox
2001-08-13 12:19   ` rui.p.m.sousa
2001-08-13 12:19 ` Alan Cox
2001-08-13 12:35 ` Alan Cox
2001-08-13 12:43   ` Tobias Ringstrom
2001-08-13 12:47 ` Anton Altaparmakov
     [not found] <997611708.29909.22.camel@DESK-2>
2001-08-12  2:52 ` Eric S. Raymond
2001-08-12 10:23   ` Jeffrey Ingber
2001-08-12 12:04     ` Alan Cox
2001-08-12 18:31       ` Manuel McLure
2001-08-12 20:15         ` Alan Cox
2001-08-12 20:30           ` Nerijus Baliunas
2001-08-12 20:35           ` Manuel McLure
2001-08-12 21:59             ` Manuel McLure
2001-08-12 22:24             ` Linus Torvalds
2001-08-12 22:55               ` Manuel McLure
2001-08-12 22:59                 ` Linus Torvalds
2001-08-12 23:15                   ` Manuel McLure
2001-08-13  0:36                     ` Paul G. Allen
2001-08-13  1:39                       ` Justin A
2001-08-13  1:00                     ` Linus Torvalds
2001-08-13  1:33                       ` Paul G. Allen
2001-08-13  1:50                         ` Nicholas Knight
2001-08-13  3:08                     ` Mike Frisch
2001-08-12 22:10           ` Linus Torvalds
2001-08-12 22:18             ` Alan Cox
2001-08-12 22:21               ` Dax Kelson
2001-08-12 22:31               ` Linus Torvalds
2001-08-16 23:28               ` Pavel Machek
2001-08-17 20:33                 ` Alan Cox
2001-08-13  3:27           ` Robert Love
2001-08-13 11:08           ` rui.p.m.sousa

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=19AB8F9FA07FB0409732402B4817D75A038A5F@FILESERVER.SRF.srfarms.com \
    --to=ryan@srfarms.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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;
as well as URLs for NNTP newsgroup(s).