public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: "Ruslan U. Zakirov" <cubic@miee.ru>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
	linux-kernel@vger.kernel.org, perex@suse.cz
Subject: Re: 2.5.57 missing isapnp_card_protocol
Date: Mon, 13 Jan 2003 18:48:48 +0000	[thread overview]
Message-ID: <20030113184848.GC605@neo.rr.com> (raw)
In-Reply-To: <Pine.BSF.4.05.10301140159310.36033-100000@wildrose.miee.ru>

On Tue, Jan 14, 2003 at 02:10:41AM +0300, Ruslan U. Zakirov wrote:
> On Mon, 13 Jan 2003, Jeff Garzik wrote:
> 
> > On Mon, Jan 13, 2003 at 02:09:49PM -0800, Adam J. Richter wrote:
> > > 	Linux-2.5.57 deletes the definition of isapnp_card_protocol
> > > and then adds some references to it.  So, the kernel does not link
> > > if you have enabled ISA PnP support.  I'm not sure whether
> > > isapnp_card_protocol is supposed to be removed or not.
> > 
> > That's the fault of some random driver that hasn't been updated to the
> > new isapnp API yet...
> 
> Hello.
> It's not right.
> It's wrong changes in drivers/pnp/isapnp/core.c and could be fixed with
> changing of two lines:
> drop 
> 	protocol_for_each_card(&isapnp_card_protocol,card)
> and change
> 	protocol_for_each_card(&isapnp_card_protocol,card)
> back to 
> 	protocol_for_each_card(&isapnp_protocol,card) 
> This changes fix compilation problems, but may be it wrong do it in this
> way.
> 
> Best regards.
> 	Ruslan.
> 

Hi Ruslan,

This is indeed a correct fix for this problem.  This bug was not introduced
by me but I appreciate your input.

Thanks,
Adam

  reply	other threads:[~2003-01-13 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 22:09 2.5.57 missing isapnp_card_protocol Adam J. Richter
2003-01-13 22:40 ` Jeff Garzik
2003-01-13 23:10   ` Ruslan U. Zakirov
2003-01-13 18:48     ` Adam Belay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-13 23:12 Adam J. Richter

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=20030113184848.GC605@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=adam@yggdrasil.com \
    --cc=cubic@miee.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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