All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] __deprecated_for_modules insert_resource
Date: Mon, 2 May 2005 03:45:58 +0200	[thread overview]
Message-ID: <20050502014558.GH3592@stusta.de> (raw)
In-Reply-To: <20050423164411.51d77bf1.akpm@osdl.org>

On Sat, Apr 23, 2005 at 04:44:11PM -0700, Andrew Morton wrote:
> 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.
>...

Patch below.

cu
Adrian


<--  snip  -->


--- linux-2.6.12-rc3-mm2-full/Documentation/feature-removal-schedule.txt.old	2005-05-01 23:59:05.000000000 +0200
+++ linux-2.6.12-rc3-mm2-full/Documentation/feature-removal-schedule.txt	2005-05-02 00:00:17.000000000 +0200
@@ -57,0 +58,8 @@
+
+---------------------------
+
+What:	remove EXPORT_SYMBOL(insert_resource)
+When:	April 2006
+Files:	kernel/resource.c
+Why:	No modular usage in the kernel.
+Who:	Adrian Bunk <bunk@stusta.de>
--- linux-2.6.12-rc3-mm2-full/include/linux/ioport.h.old	2005-05-02 00:00:30.000000000 +0200
+++ linux-2.6.12-rc3-mm2-full/include/linux/ioport.h	2005-05-02 00:00:56.000000000 +0200
@@ -97 +97 @@
-extern int insert_resource(struct resource *parent, struct resource *new);
+extern __deprecated_for_modules int insert_resource(struct resource *parent, struct resource *new);


  parent reply	other threads:[~2005-05-02  1:46 UTC|newest]

Thread overview: 7+ 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
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   ` Adrian Bunk [this message]
2005-05-02 10:54     ` [2.6 patch] __deprecated_for_modules insert_resource Arjan van de Ven

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=20050502014558.GH3592@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.