All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: wensong@linux-vs.org, netdev@oss.sgi.com
Subject: Re: [PATCHES] IPVS - use list_for_each_entry_continue, fix NQ
Date: Tue, 30 Sep 2003 01:56:59 -0700	[thread overview]
Message-ID: <20030930015659.3cc375b1.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0309271447470.2845-500000@u.domain.uli>

On Sat, 27 Sep 2003 15:02:57 +0300 (EEST)
Julian Anastasov <ja@ssi.bg> wrote:

> 	The attached patches against today's 2.6 BK tree introduce 
> list_for_each_entry_continue and use it for some IPVS schedulers. There is 
> also a NQ scheduler fix. Please consider for inclusion.

Looks good, applied.  Can you please CC: netdev@oss.sgi.com on all
patch submissions, even small and obvious ones?  Thanks.

I assume you guys are still reviewing Rusty's skb_linearize()
removal patch?

  reply	other threads:[~2003-09-30  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-27 12:02 [PATCHES] IPVS - use list_for_each_entry_continue, fix NQ Julian Anastasov
2003-09-30  8:56 ` David S. Miller [this message]
2003-09-30  9:02   ` David S. Miller
2003-09-30  9:22   ` Julian Anastasov

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=20030930015659.3cc375b1.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ja@ssi.bg \
    --cc=netdev@oss.sgi.com \
    --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 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.