public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Suardi <ALESSANDRO.SUARDI@oracle.com>
To: valdis.kletnieks@vt.edu, jochen@jochen.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.55, PCI, PCMCIA, XIRCOM]
Date: Sun, 12 Jan 2003 14:58:39 -0800 (PST)	[thread overview]
Message-ID: <1755778.1042412319026.JavaMail.nobody@web55.us.oracle.com> (raw)

> On Fri, 10 Jan 2003 20:00:31 +0100, Jochen Hein said:
> > > - and I've seen a report it causes an OOPS
> > > on 2.5.53.  I've not tried it on post-52, but I had a -54 kernel OOPS

Guess the report was mine :) note for readers, this is bug 134
 in the 2.5 kernel bug database at http://bugme.osdl.org .

> > > right around that point in bootup (right after IDE and somewhere in PCI
> > > init).  Haven't chased that one at all...
> if it OOPSes without my patch, then it's somebody else's problem.  

No, it did oops only with the patch.

[snip]

> In any case, I've attached a new *UNTESTED* patch, that only tries to
> gratuitously
> assign resources of MEM class, and disables the ROM once it does so.
> No, I don't claim to fully understand this code.  And if you're not brave
> enough or can't test it yourself, I'll be taking the 2.5.56 plunge sometime
> this weekend. ;)  And all you other kernel hackers are welcome to jump right
> in and tell me what I'm doing wrong.. ;)

-ENOPATCH ;)


Ciao,

--alessandro

             reply	other threads:[~2003-01-12 22:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12 22:58 Alessandro Suardi [this message]
2003-01-12 23:16 ` [2.5.55, PCI, PCMCIA, XIRCOM] Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2003-01-10 16:21 Jochen Hein
2003-01-10 17:13 ` Valdis.Kletnieks
2003-01-10 19:00   ` Jochen Hein
2003-01-10 22:17     ` Valdis.Kletnieks

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=1755778.1042412319026.JavaMail.nobody@web55.us.oracle.com \
    --to=alessandro.suardi@oracle.com \
    --cc=jochen@jochen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=valdis.kletnieks@vt.edu \
    /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