netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lightweight patch manager <patch@luckynet.dynu.com>
To: Linux Network <linux-net@vger.kernel.org>
Cc: Linux Networking Team <netdev@oss.sgi.com>
Subject: [PATCH][2.5] list_move_tail for sunrpc (1 occ)
Date: Sun, 9 Jun 2002 09:04:15 -0600 (MDT)	[thread overview]
Message-ID: <advqu5$e04$2@main.gmane.org> (raw)

This patch introduces the new list_move_tail macro for the sunrpc driver
(net/sunrpc/svcsock.c)

--- linus-2.5/net/sunrpc/svcsock.c	Sun Jun  9 04:17:42 2002
+++ thunder-2.5/net/sunrpc/svcsock.c	Sun Jun  9 07:43:53 2002
@@ -1065,8 +1065,7 @@
 	if (test_bit(SK_TEMP, &svsk->sk_flags)) {
 		/* push active sockets to end of list */
 		spin_lock_bh(&serv->sv_lock);
-		list_del(&svsk->sk_list);
-		list_add_tail(&svsk->sk_list, &serv->sv_tempsocks);
+		list_move_tail(&svsk->sk_list, &serv->sv_tempsocks);
 		spin_unlock_bh(&serv->sv_lock);
 	}
 

-- 
Lightweight patch manager using pine. If you have any objections, tell me.

                 reply	other threads:[~2002-06-09 15:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='advqu5$e04$2@main.gmane.org' \
    --to=patch@luckynet.dynu.com \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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).