public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: kernel-janitor-discuss@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: privatize various functions in sched.h
Date: Fri, 15 Nov 2002 11:07:10 -0800	[thread overview]
Message-ID: <20021115190710.GA23425@holomorphy.com> (raw)
In-Reply-To: <20021115112836.GU23425@holomorphy.com>

On Fri, Nov 15, 2002 at 02:54:03AM -0800, William Lee Irwin III wrote:
>> This removes a bunch of inlines used only in isolated places from sched.h

On Fri, Nov 15, 2002 at 03:28:36AM -0800, William Lee Irwin III wrote:
> Hmm, while I'm at it, this applies atop the previous patch:
> This removes d_path() from sched.h and uninlines it. No idea why it was
> in sched.h in the first place (or why something this large is inlined).

Atop the d_path() removal patch:


__d_path() may be privatized since umsdos is broken anyway.

 fs/dcache.c            |    6 +++---
 include/linux/dcache.h |    2 --
 kernel/ksyms.c         |    1 -
 3 files changed, 3 insertions(+), 6 deletions(-)


diff -urpN cleanup-2.5.47-5/fs/dcache.c cleanup-2.5.47-6/fs/dcache.c
--- cleanup-2.5.47-5/fs/dcache.c	2002-11-15 02:45:02.000000000 -0800
+++ cleanup-2.5.47-6/fs/dcache.c	2002-11-15 10:19:33.000000000 -0800
@@ -1136,9 +1136,9 @@ void d_move(struct dentry * dentry, stru
  *
  * "buflen" should be %PAGE_SIZE or more. Caller holds the dcache_lock.
  */
-char * __d_path(struct dentry *dentry, struct vfsmount *vfsmnt,
-		struct dentry *root, struct vfsmount *rootmnt,
-		char *buffer, int buflen)
+static char * __d_path( struct dentry *dentry, struct vfsmount *vfsmnt,
+			struct dentry *root, struct vfsmount *rootmnt,
+			char *buffer, int buflen)
 {
 	char * end = buffer+buflen;
 	char * retval;
diff -urpN cleanup-2.5.47-5/include/linux/dcache.h cleanup-2.5.47-6/include/linux/dcache.h
--- cleanup-2.5.47-5/include/linux/dcache.h	2002-11-15 02:41:37.000000000 -0800
+++ cleanup-2.5.47-6/include/linux/dcache.h	2002-11-15 10:19:01.000000000 -0800
@@ -238,8 +238,6 @@ extern struct dentry * __d_lookup(struct
 /* validate "insecure" dentry pointer */
 extern int d_validate(struct dentry *, struct dentry *);
 
-extern char * __d_path(struct dentry *, struct vfsmount *, struct dentry *,
-	struct vfsmount *, char *, int);
 extern char * d_path(struct dentry *, struct vfsmount *, char *, int);
   
 /* Allocation counts.. */
diff -urpN cleanup-2.5.47-5/kernel/ksyms.c cleanup-2.5.47-6/kernel/ksyms.c
--- cleanup-2.5.47-5/kernel/ksyms.c	2002-11-15 02:43:58.000000000 -0800
+++ cleanup-2.5.47-6/kernel/ksyms.c	2002-11-15 10:19:50.000000000 -0800
@@ -167,7 +167,6 @@ EXPORT_SYMBOL(d_alloc_anon);
 EXPORT_SYMBOL(d_splice_alias);
 EXPORT_SYMBOL(d_lookup);
 EXPORT_SYMBOL(d_path);
-EXPORT_SYMBOL(__d_path);
 EXPORT_SYMBOL(mark_buffer_dirty);
 EXPORT_SYMBOL(end_buffer_io_sync);
 EXPORT_SYMBOL(__mark_inode_dirty);

  reply	other threads:[~2002-11-15 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 10:54 privatize various functions in sched.h William Lee Irwin III
2002-11-15 11:28 ` William Lee Irwin III
2002-11-15 19:07   ` William Lee Irwin III [this message]
2002-11-15 12:49 ` William Lee Irwin III

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=20021115190710.GA23425@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=kernel-janitor-discuss@lists.sourceforge.net \
    --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