From: Adrian Bunk <bunk@stusta.de>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: David Miller <davem@davemloft.net>,
neilb@cse.unsw.edu.au, trond.myklebust@fys.uio.no,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
netdev@vger.kernel.org
Subject: Re: [NFS] [RFC: 2.6 patch] net/sunrpc/: possible cleanups
Date: Sat, 15 Apr 2006 23:32:15 +0200 [thread overview]
Message-ID: <20060415213215.GN15022@stusta.de> (raw)
In-Reply-To: <044B81DE141D7443BCE91E8F44B3C1E288E4FC@exsvl02.hq.netapp.com>
On Thu, Oct 06, 2005 at 07:13:14AM -0700, Lever, Charles wrote:
> actually, can we hold off on this change? the RPC transport switch will
> eventually need most of those EXPORT_SYMBOLs.
>...
> > This patch was already sent on:
> > - 30 May 2005
> > - 7 May 2005
>...
One year has passed since I sent this patch the first time, and with the
exception that it needs re-diff'ing it still applies.
Charles, are the changes you are talking about that might need them
available in the very near future?
If not, I'd suggest to remove them and re-add them when code using them
will be included in the kernel (reverting parts or all of my patch
should be trivial).
This way, they'll not continue to uselessly making the kernel image
larger.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-04-15 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 14:13 [NFS] [RFC: 2.6 patch] net/sunrpc/: possible cleanups Lever, Charles
2005-11-23 1:24 ` [2.6 patch] net/sunrpc/xdr.c: remove xdr_decode_string() Adrian Bunk
2006-04-15 21:32 ` Adrian Bunk [this message]
2006-04-15 23:01 ` [NFS] [RFC: 2.6 patch] net/sunrpc/: possible cleanups Lever, Charles
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=20060415213215.GN15022@stusta.de \
--to=bunk@stusta.de \
--cc=Charles.Lever@netapp.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=netdev@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).