All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Feiler <kiza@gmx.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: [Patch] (was: Re: fixup descriptions in pci-pc.c)
Date: Mon, 4 Feb 2002 11:46:44 +0100	[thread overview]
Message-ID: <20020204114644.A331@gmx.net> (raw)
In-Reply-To: <20020203152913.A533@gmx.net> <Pine.LNX.4.30.0202032342400.1158-100000@rtlab.med.cornell.edu>
In-Reply-To: <Pine.LNX.4.30.0202032342400.1158-100000@rtlab.med.cornell.edu>; from calin@ajvar.org on Sun, Feb 03, 2002 at 11:49:42PM -0500

Hello,

	This just changes the printk in the via_northbridge_bug fixup to some 
more meaningful output as it is already in 2.5.3. Please apply.

Oliver

--- linux-2.4.18-pre7/arch/i386/kernel/pci-pc.c	Sun Feb  3 14:56:48 2002
+++ linux-2.4.18-pre7_testing/arch/i386/kernel/pci-pc.c	Mon Feb  4 11:30:37 2002
@@ -1129,7 +1129,7 @@
 
 	pci_read_config_byte(d, where, &v);
 	if (v & 0xe0) {
-		printk("Trying to stomp on VIA Northbridge bug...\n");
+		printk("Disabling broken memory write queue.\n");
 		v &= 0x1f; /* clear bits 5, 6, 7 */
 		pci_write_config_byte(d, where, v);
 	}


-- 
Oliver Feiler                                               kiza@gmx.net
http://www.lionking.org/~kiza/pgpkey              PGP key ID: 0x561D4FD2
http://www.lionking.org/~kiza/

  reply	other threads:[~2002-02-04 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-03 14:29 fixup descriptions in pci-pc.c Oliver Feiler
2002-02-04  4:49 ` Calin A. Culianu
2002-02-04 10:46   ` Oliver Feiler [this message]
2002-02-04 10:19     ` [Patch] (was: Re: fixup descriptions in pci-pc.c) Ragnar Hojland Espinosa
2002-02-04 15:09     ` Calin A. Culianu
2002-02-04 17:11 ` fixup descriptions in pci-pc.c Denis Vlasenko
2002-02-04 14:49   ` Oliver Feiler
2002-02-04 18:55     ` Denis Vlasenko

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=20020204114644.A331@gmx.net \
    --to=kiza@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.