To: Greg KH <greg@kroah.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EISA bus update
Organization: Metropolis -- Nowhere
Reply-to: mzyngier@freesurf.fr
References: <wrp3cfxn78n.fsf@hina.wild-wind.fr.eu.org>
	<20030819174208.GA4992@kroah.com>
From: Marc Zyngier <mzyngier@freesurf.fr>
Date: Tue, 19 Aug 2003 20:16:12 +0200
Message-ID: <wrpptj1fr83.fsf@hina.wild-wind.fr.eu.org>
In-Reply-To: <20030819174208.GA4992@kroah.com> (Greg KH's message of "Tue,
 19 Aug 2003 10:42:08 -0700")
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1079
Lines: 25

>>>>> "Greg" == Greg KH <greg@kroah.com> writes:

Greg,

Greg> Marc, why do you think that you do not need to do anything in
Greg> this function?  Don't you need to handle the fact that your code
Greg> could be removed before the release function is called?

Well, there is nothing to do in this function, because that's what the
whole driver does: nothing. It just presents a range of IO ports to be
probed to the main EISA code, and nothing else.

If the driver is removed from the kernel (which can't happen at the
moment, since it is not modular), it doesn't matter... Once it has
registered as an EISA bus root, it doesn't get called anymore, the
core code does it all by itself.

So no, I truly don't think there's anything to do in this release
function.

Regards,

	M.
-- 
Places change, faces change. Life is so very strange.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/