From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: ja@ssi.bg, wensong@linux-vs.org,
lvs-users@LinuxVirtualServer.org, netdev@oss.sgi.com
Subject: Re: [PATCH] ipvs -- fix error's in list_for_each changes.
Date: Tue, 23 Sep 2003 03:59:51 -0700 [thread overview]
Message-ID: <20030923035951.63d89345.davem@redhat.com> (raw)
In-Reply-To: <20030922112204.225e1a98.shemminger@osdl.org>
On Mon, 22 Sep 2003 11:22:04 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> The earlier list_for_each changes introduced a couple of bugs where
> lines got dropped. This restores them.
Applied, thanks Stephen.
prev parent reply other threads:[~2003-09-23 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 21:17 [PATCH] (3/6) ipvs -- use list_for_each_entry macro's Stephen Hemminger
2003-09-20 8:06 ` David S. Miller
2003-09-21 7:54 ` Julian Anastasov
2003-09-22 18:03 ` Stephen Hemminger
2003-09-22 22:38 ` Julian Anastasov
2003-09-22 18:22 ` [PATCH] ipvs -- fix error's in list_for_each changes Stephen Hemminger
2003-09-23 10:59 ` David S. Miller [this message]
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=20030923035951.63d89345.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=lvs-users@LinuxVirtualServer.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
--cc=wensong@linux-vs.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;
as well as URLs for NNTP newsgroup(s).