From: Greg KH <greg@kroah.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: removal of EXPORT_SYMBOL(insert_resource)?
Date: Fri, 3 Mar 2006 16:59:35 -0800 [thread overview]
Message-ID: <20060304005935.GA27548@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0603021316001.307-100000@gate.crashing.org>
On Thu, Mar 02, 2006 at 01:31:08PM -0600, Kumar Gala wrote:
> I have a situation that I believe warrants leaving insert_resource as an
> exported API.
>
> I've got a bus implementation that it done as a module. While I'm more
> than happy to provide this bus implementation to be included in the
> mainline, I dont think it makes much sense to do so. The code is only
> useful to an extremely small handful of people. If we want to clutter the
> kernel with it I'm happy to provide a patch for it.
Please do, keeping code outside the kernel makes it _very_ hard on you.
It makes it easier if everything is in-the-tree, as you know.
Hell, we have two whole x86 subarchs with only 4 machines each in
existance, a simple bus is nothing :)
> The situation I have is a FPGA connect over PCI. The FPGA implements a
> number of different "functions" but uses PCI more like an SoC bus than a
> true PCI device. Anyways, in some discussions with gregkh, it was
> suggested the best thing was to create a new bus type that the "fpga"
> drivers would bind to.
>
> I use insert_resource to handle registering the MMIO regions for each
> device (similar to how platform devices are registered).
All the better reason to get it into the tree...
thanks,
greg k-h
next prev parent reply other threads:[~2006-03-04 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 19:31 removal of EXPORT_SYMBOL(insert_resource)? Kumar Gala
2006-03-04 0:59 ` Greg KH [this message]
2006-04-01 10:46 ` Adrian Bunk
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=20060304005935.GA27548@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
/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