From: Oliver Feiler <kiza@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: fixup descriptions in pci-pc.c
Date: Sun, 3 Feb 2002 15:29:13 +0100 [thread overview]
Message-ID: <20020203152913.A533@gmx.net> (raw)
Ok, this is just a cosmetic thing, but I see that in 2.5.3 the printk
text in pci_fixup_via_northbridge_bug in pci-pc.c was changed
- printk("Trying to stomp on VIA Northbridge bug...\n");
+ printk("Disabling broken memory write queue.\n");
Can't we change this to some meaningful output in 2.4.18 as well? It's
still the old text with pre7.
Bye
Oliver
--
Oliver Feiler kiza@gmx.net
http://www.lionking.org/~kiza/pgpkey PGP key ID: 0x561D4FD2
http://www.lionking.org/~kiza/
next reply other threads:[~2002-02-03 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 14:29 Oliver Feiler [this message]
2002-02-04 4:49 ` fixup descriptions in pci-pc.c Calin A. Culianu
2002-02-04 10:46 ` [Patch] (was: Re: fixup descriptions in pci-pc.c) Oliver Feiler
2002-02-04 10:19 ` 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=20020203152913.A533@gmx.net \
--to=kiza@gmx.net \
--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