Date: Tue, 25 Jan 2005 19:10:50 -0800
From: Andrew Morton <akpm@osdl.org>
To: paulmck@us.ibm.com
Cc: arjan@infradead.org, trond.myklebust@fys.uio.no, viro@zenII.uk.linux.org,
       linux-kernel@vger.kernel.org
Subject: Re: make flock_lock_file_wait static
Message-Id: <20050125191050.68fb0cdf.akpm@osdl.org>
In-Reply-To: <20050125185812.GA1499@us.ibm.com>
References: <20050109194209.GA7588@infradead.org>
	<1105310650.11315.19.camel@lade.trondhjem.org>
	<1105345168.4171.11.camel@laptopd505.fenrus.org>
	<1105346324.4171.16.camel@laptopd505.fenrus.org>
	<1105367014.11462.13.camel@lade.trondhjem.org>
	<1105432299.3917.11.camel@laptopd505.fenrus.org>
	<1105471004.12005.46.camel@lade.trondhjem.org>
	<1105472182.3917.49.camel@laptopd505.fenrus.org>
	<20050125185812.GA1499@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 776
Lines: 22

"Paul E. McKenney" <paulmck@us.ibm.com> wrote:
>
>  So, could the exports for the following symbols from the list please be
>  retained through December 31, 2005?
> 
>  	blk_get_queue
>  	sock_setsockopt
>  	vfs_follow_link
>  	__read_lock_failed
>  	__write_lock_failed

I don't think there's any plan to unexport any of these, and in most cases
it would be a dopey thing to do anyway.  And if we _were_ to try to remove
any of the above exports we should go through the
feature-removal-schedule.txt process.

So I think we're OK?
-
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/