From: Christian Kujau <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Subject: Re: parport_pc Oops with 2.6.0-test3
Date: Thu, 28 Aug 2003 04:41:09 +0200 [thread overview]
Message-ID: <3F4D6BC5.3050901@g-house.de> (raw)
In-Reply-To: <20030826013829.73d00992.akpm@osdl.org>
Andrew Morton wrote:
> --- 25/drivers/parport/parport_pc.c~parport_pc-rmmod-oops-fix 2003-08-26 01:32:59.000000000 -0700
> +++ 25-akpm/drivers/parport/parport_pc.c 2003-08-26 01:33:08.000000000 -0700
> @@ -93,7 +93,7 @@ static struct superio_struct { /* For Su
> int dma;
> } superios[NR_SUPERIOS] __devinitdata = { {0,},};
>
> -static int user_specified __devinitdata = 0;
> +static int user_specified;
> #if defined(CONFIG_PARPORT_PC_SUPERIO) || \
> (defined(CONFIG_PARPORT_1284) && defined(CONFIG_PARPORT_PC_FIFO))
> static int verbose_probing;
ah, that did it. now i get
parport0: PC-style at 0x378 (0x778), irq 7, using FIFO \
[PCSPP,TRISTATE,COMPAT,ECP]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
upon loading of parport_pc and no oops when unloading (tried it several
times, even with a tainted kernel.)
you know, even tiny patches like this (a single line changed!) look
quite incredible to a non hacker (me). with this little bits of
information i gave you, you produced a working patch. this is...totally
cool, really.
Thank you very much,
Christian.
--
BOFH excuse #312:
incompatible bit-registration operators
next prev parent reply other threads:[~2003-08-28 0:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 8:38 increased verbosity in dmesg Gene Heskett
2003-08-16 10:48 ` Martin Schlemmer
2003-08-16 12:51 ` Arkadiusz Miskiewicz
2003-08-16 15:07 ` Gene Heskett
2003-08-26 0:17 ` parport_pc Oops with 2.6.0-test3 Christian Kujau
2003-08-26 8:38 ` Andrew Morton
2003-08-26 23:03 ` Christian
2003-08-28 2:41 ` Christian Kujau [this message]
2003-08-16 11:02 ` increased verbosity in dmesg Felipe Alfaro Solana
2003-08-16 15:36 ` Gene Heskett
2003-08-16 15:45 ` Felipe Alfaro Solana
2003-08-16 16:01 ` Gene Heskett
2003-08-16 16:24 ` Felipe Alfaro Solana
2003-08-16 17:41 ` Randy.Dunlap
2003-08-16 17:57 ` Gene Heskett
2003-08-16 17:18 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 11:20 parport_pc Oops with 2.6.0-test3 Christian Kujau
2003-08-19 22:01 ` Christian Kujau
2003-08-24 10:00 ` Andrew Morton
2003-08-24 14:34 ` Christian
2003-08-25 4:53 ` Christian Kujau
2003-08-25 3:37 ` Andrew Morton
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=3F4D6BC5.3050901@g-house.de \
--to=evil@g-house.de \
--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