public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Adam Belay <ambx1@neo.rr.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] proposed PnP layer changes/fixes and cleanups
Date: Mon, 30 Dec 2002 14:09:12 -0800	[thread overview]
Message-ID: <20021230220911.GD32324@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212201557270.824-100000@pnote.perex-int.cz>

On Sun, Dec 29, 2002 at 12:20:15PM +0100, Jaroslav Kysela wrote:
> Hi,
> 
> 	I've revised the PnP code and found numerous of simple bugs. Also,
> my opinion is that the resctriction of resources to only ones hardcoded by
> hardware vendors is not a good idea. Hardware usually supports more
> configurations (especially ISA PnP devices).
> 	I've tried to implement a configuration template, so driver can
> pass it's own resource map in the probe phase. Also, I've added a new
> member to the driver structures - flags. The flag
> PNP_DRIVER_DO_NOT_ACTIVATE instructs the pnp code that the device
> shouldn't be activated before the probe() callback is entered. It's
> necessary to implement this behaviour to allow passing of a new
> configuration template (thus calling pnp_activate_dev() from the probe()
> callback).
> 	Also, the resources can be locked now (I've changed the ro flag to 
> lock_resources).

These changes look good, I'll send them on to Linus.

thanks,

greg k-h

  reply	other threads:[~2002-12-30 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-29 11:20 [PATCH] proposed PnP layer changes/fixes and cleanups Jaroslav Kysela
2002-12-30 22:09 ` Greg KH [this message]
2002-12-31 16:49   ` Adam Belay

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=20021230220911.GD32324@kroah.com \
    --to=greg@kroah.com \
    --cc=ambx1@neo.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.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