From: Wakko Warner <wakko@animx.eu.org>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, akpm <akpm@osdl.org>,
linux@dominikbrodowski.net
Subject: Re: [PATCH] pcmcia/ds: handle any error code
Date: Fri, 13 May 2005 15:45:49 -0400 [thread overview]
Message-ID: <20050513194549.GB3519@animx.eu.org> (raw)
In-Reply-To: <20050512222038.325081b2.rdunlap@xenotime.net>
randy_dunlap wrote:
> On Thu, 12 May 2005 19:02:06 -0400 Wakko Warner wrote:
> There is some small difference in locking in fs/char_dev.c between
> 2.6.12-rc4 and 2.6.11.8, but I don't yet see why it would cause a
> failure in register_chrdev().
>
> Oh, there's a big difference in drivers/pcmcia/ds.c, lots of probe
> changes. This is where to look further (but not tonight).
> The question then becomes is this a real regression?
>
> Do you suspect a problem with -Os code generation?
I just tried it, it doesn't give me any errors. This is strange considering
that I a) use a pristine tree for each kernel (only coping the .config) and
b) the patch doesn't do anything except report the error. I made my boot
floppy (the scripts I use pull from the kernel tree I specify and make the
image I need) and booted from it. I placed the modules on my stage2 disk
that was made and it works.
I don't have the time this week to try again from scratch. I'll see if I
can do it next week.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2005-05-13 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 1:52 Bugs in 2.6.12-rc kernels Wakko Warner
2005-05-12 23:02 ` Wakko Warner
2005-05-13 5:20 ` [PATCH] pcmcia/ds: handle any error code randy_dunlap
2005-05-13 10:50 ` Wakko Warner
2005-05-13 19:45 ` Wakko Warner [this message]
2005-05-14 17:22 ` randy_dunlap
2005-05-14 17:26 ` Wakko Warner
2005-05-14 17:32 ` randy_dunlap
2005-06-07 2:09 ` Wakko Warner
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=20050513194549.GB3519@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rdunlap@xenotime.net \
/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
all inboxes | Powered by JetHome®