All of lore.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@lovecn.org>
To: tao@acc.umu.se, linux-kernel@vger.kernel.org
Subject: [PATCH 2.0.39] put_last_free() defined, but not used
Date: Mon, 26 Jan 2004 03:23:15 +0800	[thread overview]
Message-ID: <401417A3.7000206@lovecn.org> (raw)

Hello,

In 2.0.39, the function put_last_free() in fs/file_table.c is defined, 
but no longer get used.
Should it be removed?

thanks


--- fs/file_table.c.orig    1994-10-21 07:39:36.000000000 +0800
+++ fs/file_table.c    2004-01-26 03:10:38.000000000 +0800
@@ -52,20 +52,6 @@
     prev->f_next = next;
 }
 
-/*
- * Insert a file structure at the end of the list of available ones.
- */
-static inline void put_last_free(struct file *file)
-{
-    struct file *next, *prev;
-
-    next = first_file;
-    file->f_next = next;
-    prev = next->f_prev;
-    next->f_prev = file;
-    file->f_prev = prev;
-    prev->f_next = file;
-}
 
 /*
  * Allocate a new memory page for file structures and


             reply	other threads:[~2004-01-25 19:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 19:23 Coywolf Qi Hunt [this message]
2004-01-25 22:29 ` [PATCH 2.0.39] put_last_free() defined, but not used David Weinehall
2004-01-25 23:43   ` Jens Axboe
2004-01-26  2:01     ` David Weinehall
2004-01-27 17:10   ` [2.0.40-rc8] Works well Markus Hästbacka
2004-01-27 17:38     ` David Weinehall
2004-01-28  3:28     ` Coywolf Qi Hunt
2004-01-28  3:37       ` David Weinehall
2004-01-28  6:13         ` Markus Hästbacka
2004-01-28 15:17           ` David Weinehall
2004-01-28 23:37             ` Markus Hästbacka
2004-01-28 23:50               ` David Weinehall
2004-02-23  6:28         ` about 2.0 cleanup or adaption Coywolf Qi Hunt
2004-03-03 13:38         ` [PATCH 2.0.40] Fix comment error of prepare_binprm() in exec.c Coywolf Qi Hunt
2004-03-03 13:51           ` David Weinehall

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=401417A3.7000206@lovecn.org \
    --to=coywolf@lovecn.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tao@acc.umu.se \
    /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.