From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] unexport insert_resource
Date: Sat, 23 Apr 2005 16:44:11 -0700 [thread overview]
Message-ID: <20050423164411.51d77bf1.akpm@osdl.org> (raw)
In-Reply-To: <20050415151043.GJ5456@stusta.de>
Adrian Bunk <bunk@stusta.de> wrote:
>
> I didn't find any possible modular usage in the kernel.
>
True, but this looks like something which out-of-tree code could possibly
be using. I'd prefer to see this one get the deprecated_for_modules
twelve-month treatment.
Or we just leave it as-is. It depends whether insert_resource is a
sensible part of the resource management API (I think it is). If so,
then we should just leave it exported, whether or not any in-kernel moduels
happen to be using it at this point in time.
>
> --- linux-2.6.11-rc5-mm1-full/kernel/resource.c.old 2005-03-04 01:01:30.000000000 +0100
> +++ linux-2.6.11-rc5-mm1-full/kernel/resource.c 2005-03-04 01:01:42.000000000 +0100
> @@ -371,8 +371,6 @@
> return result;
> }
>
> -EXPORT_SYMBOL(insert_resource);
> -
> /*
> * Given an existing resource, change its start and size to match the
> * arguments. Returns -EBUSY if it can't fit. Existing children of
next prev parent reply other threads:[~2005-04-23 23:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 15:10 [2.6 patch] unexport insert_resource Adrian Bunk
2005-04-23 23:44 ` Andrew Morton [this message]
2005-04-24 8:58 ` Arjan van de Ven
2005-04-24 9:52 ` Christoph Hellwig
2005-04-24 10:14 ` Andrew Morton
2005-05-02 1:45 ` [2.6 patch] __deprecated_for_modules insert_resource Adrian Bunk
2005-05-02 10:54 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 0:48 [2.6 patch] unexport insert_resource 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=20050423164411.51d77bf1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--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