mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, linux@dominikbrodowski.net
Subject: Re: [PATCH] pcmcia/ds: handle any error code
Date: Sat, 14 May 2005 13:26:19 -0400	[thread overview]
Message-ID: <20050514172619.GA5835@animx.eu.org> (raw)
In-Reply-To: <20050514102213.3440c526.rdunlap@xenotime.net>

randy_dunlap wrote:
> On Fri, 13 May 2005 15:45:49 -0400 Wakko Warner wrote:
> | 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.
> 
> I'm currently running a kernel built with -Os.  I can successfully
> load pcmcia_core.ko and pcmcia.ko.  I added debug printk's in
> drivers/pcmcia/ds.c and it allocates the dynamic major dev
> successfully:

I noticed this too.  I can't figure out why it wasn't working before.  I
don't believe the method of loading the kernel (hdd, usb, floppy) would
cause this.  Next week when I get a chance to work more on this project,
I'll wipe out my entire kernel tree (saving the .config) and try again (I
keep pristine sources in /usr/src/linux/dist/<kernel vers>)

> What gcc version are you using?  (gcc 4.0 has a few known issues.)

gcc (GCC) 3.4.4 20050314 (prerelease) (Debian 3.4.3-12)

I have gcc-3.3 also installed.  Should I use it instead?

I follow the list somewhat (only interesting sujects =) and I have noticed
that 4.0 has some problems.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2005-05-14 17:27 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
2005-05-14 17:22       ` randy_dunlap
2005-05-14 17:26         ` Wakko Warner [this message]
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=20050514172619.GA5835@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®