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
Date: Tue, 25 Jan 2005 19:10:50 -0800 [thread overview]
Message-ID: <20050125191050.68fb0cdf.akpm@osdl.org> (raw)
In-Reply-To: <20050125185812.GA1499@us.ibm.com>
"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?
next prev parent reply other threads:[~2005-01-26 3:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 19:42 make flock_lock_file_wait static Arjan van de Ven
2005-01-09 22:44 ` Trond Myklebust
2005-01-10 8:19 ` Arjan van de Ven
2005-01-10 8:38 ` Arjan van de Ven
2005-01-10 14:23 ` Trond Myklebust
2005-01-11 8:31 ` Arjan van de Ven
2005-01-11 19:16 ` Trond Myklebust
2005-01-11 19:36 ` Arjan van de Ven
2005-01-25 18:58 ` Paul E. McKenney
2005-01-26 3:10 ` Andrew Morton [this message]
2005-01-26 9:01 ` Arjan van de Ven
2005-01-26 16:07 ` Paul E. McKenney
2005-01-26 18:59 ` Arjan van de Ven
2005-01-28 14:14 ` Paul E. McKenney
2005-01-28 18:50 ` Christoph Hellwig
2005-01-28 19:01 ` Arjan van de Ven
2005-01-26 9:43 ` Christoph Hellwig
2005-01-26 9:51 ` Al Viro
2005-01-26 9:55 ` Christoph Hellwig
2005-01-26 10:00 ` Al Viro
2005-01-15 21:35 ` Adrian Bunk
2005-01-15 22:07 ` Trond Myklebust
2005-01-10 8:35 ` Ken Preslan
2005-01-10 8:44 ` 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=20050125191050.68fb0cdf.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@zenII.uk.linux.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.