netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] UDP/IPv6 multicasting
Date: Mon, 17 Nov 2003 12:41:04 -0800	[thread overview]
Message-ID: <20031117124104.570e1c72.davem@redhat.com> (raw)
In-Reply-To: <OF974281CA.F4EE30F2-ON88256DDE.007F34F9@us.ibm.com>

On Fri, 14 Nov 2003 16:11:50 -0700
David Stevens <dlstevens@us.ibm.com> wrote:

>       Below is a patch to fix a problem reported by Brian Buesker. When
> binding to
> two different multicast addresses on the same UDP port, a copy sent to
> either multicast
> address is delivered to both.

Thanks a lot David, I will review and probably apply this later
on today.

2.4.x has identical code in this spot so I'll put the fix there
as well and queue it up for 2.4.24-pre1.

Thanks again.

      reply	other threads:[~2003-11-17 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 23:11 [PATCH] UDP/IPv6 multicasting David Stevens
2003-11-17 20:41 ` 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=20031117124104.570e1c72.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=dlstevens@us.ibm.com \
    --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).