public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: alex@PolesApart.wox.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131
Date: Mon, 24 Jun 2002 08:04:09 -0700 (PDT)	[thread overview]
Message-ID: <20020624.080409.79615643.davem@redhat.com> (raw)
In-Reply-To: <3D173578.5080205@PolesApart.wox.org>

   From: "Alexandre P. Nunes" <alex@PolesApart.wox.org>
   Date: Mon, 24 Jun 2002 12:06:32 -0300
   
   Maybe I got it the wrong way, but it seems to me that from your point of 
   view, as long as proprietary driver is in use, it's not anyone else 
   problem but to the vendor, even if the bug could happen to be in the 
   kernel, is that right? If so, everyone else in this list who could try 
   to fix this (again assuming it could be something related to the kernel 
   and not to the proprietary driver) necessarily share your oppinion? (I'm 
   not flaming in here, just trying to get the path).

This has to do with facts, not opinions.  Since we lack the source to
their drivers, we have no idea if some bug in their driver is
scribbling over (ie. corrupting) memory.  It is therefore an unknown
which makes it a waste of time for us to pursue the bug report.

  reply	other threads:[~2002-06-24 15:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200206231945.27717.markus_schoder@yahoo.de>
2002-06-24 12:23 ` PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131 Alexandre P. Nunes
2002-06-24 14:17   ` Alan Cox
2002-06-24 15:06     ` Alexandre P. Nunes
2002-06-24 15:04       ` David S. Miller [this message]
2002-06-24 16:47         ` Alexandre P. Nunes
2002-07-01  2:18         ` Pavel Machek
2002-07-02  1:39           ` Horst von Brand
2002-07-02 16:29         ` Bill Davidsen
2002-07-02 17:04           ` Alexandre P. Nunes
2002-07-02 23:25             ` Matthias Andree
2002-06-24 15:18       ` Zwane Mwaikambo
2002-06-23  1:13 Alexandre Pereira Nunes
2002-06-23 11:07 ` Diego Calleja
2002-06-23 11:40   ` Alexandre Pereira Nunes
2002-06-26 20:47 ` William Lee Irwin III
2002-06-26 21:00   ` Bongani
2002-06-26 21:45     ` khromy
2002-06-26 21:54     ` Robert Love
2002-06-26 22:12       ` Bongani
2002-06-26 22:08         ` Robert Love
2002-06-27  0:54       ` William Lee Irwin III
2002-06-27 15:40         ` Robert Love
2002-06-27 15:47           ` William Lee Irwin III
2002-06-27 18:29             ` Alexandre P. Nunes
2002-06-27 18:31               ` Robert Love
2002-06-27 18:53                 ` Alexandre P. Nunes
2002-06-27 20:05                   ` J Sloan

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=20020624.080409.79615643.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=alex@PolesApart.wox.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox