netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: dlstevens@us.ibm.com
Cc: netdev@oss.sgi.com, stevenh@xsmail.com
Subject: Re: multicast loop with include filters fix [PATCH]
Date: Sat, 24 Jan 2004 10:00:39 -0800 (PST)	[thread overview]
Message-ID: <20040124.100039.59476360.davem@redhat.com> (raw)
In-Reply-To: <OF62EF6DA6.732A9C7E-ON88256E24.007C1F78@us.ibm.com>

   From: David Stevens <dlstevens@us.ibm.com>
   Date: Fri, 23 Jan 2004 15:39:26 -0700

         Here's the 2.4.x version of the patch.

Both 2.4.x and 2.6.x variants applied, thanks David.

I assume the 2.4.x patch had the small fixup the original
2.6.x one needed.

  reply	other threads:[~2004-01-24 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 22:39 multicast loop with include filters fix [PATCH] David Stevens
2004-01-24 18:00 ` David S. Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-23 20:27 David Stevens
2004-01-23  2:02 David Stevens
2004-01-23  1:57 ` David S. Miller

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=20040124.100039.59476360.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev@oss.sgi.com \
    --cc=stevenh@xsmail.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).