mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: Kernel 2.6.9 Multiple Page Allocation Failures (Part 2)
Date: Wed, 27 Oct 2004 20:33:09 -0400	[thread overview]
Message-ID: <1098923590.1514.16.camel@krustophenia.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0410271733440.10927@p500>

On Wed, 2004-10-27 at 17:40 -0400, Justin Piszcz wrote:
> Is there any chance Linus will freeze 2.6 and make the current development 
> tree 2.7?  It seems like ever since around 2.6.8 things have been getting 
> progressively worse (page allocation failures/nvidia 
> breakage/XFS-oops-when-copying-over-nfs-when-the-file-is-being-written-to)?

This not the kernel's problem when nvidia breaks.  The kernel developers
make NO EFFORT to support binary only modules!  Please, talk to nvidia
if this is a problem for you.

Lee


  parent reply	other threads:[~2004-10-28  0:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25 10:48 Kernel 2.6.9 Page Allocation Failures w/TSO+rollup.patch Justin Piszcz
2004-10-25 11:33 ` Nick Piggin
2004-10-25 12:03   ` Justin Piszcz
2004-10-27 21:40   ` Kernel 2.6.9 Multiple Page Allocation Failures (Part 2) Justin Piszcz
2004-10-27 21:58     ` Andrew Morton
2004-10-27 21:55       ` Justin Piszcz
2004-10-27 22:19         ` Francois Romieu
2004-10-27 22:23           ` Justin Piszcz
2004-10-28  0:33     ` Lee Revell [this message]
2004-11-03 22:24 Stefan Schmidt
2004-11-04 12:17 ` Marcelo Tosatti
2004-11-04 18:18   ` Stefan Schmidt

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=1098923590.1514.16.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=akpm@osdl.org \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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

Powered by JetHome