All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moni Shoua <monis-hKgKHo2Ms0F+cjeuK/JdrQ@public.gmane.org>
To: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
Cc: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
	Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
	linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: How to handle illegal multicast addresses in IPoIB?
Date: Mon, 21 Sep 2009 17:39:11 +0300	[thread overview]
Message-ID: <4AB7900F.2020406@Voltaire.COM> (raw)
In-Reply-To: <4AB78EC9.7020805-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>

Or Gerlitz wrote:
> Moni Shoua wrote:
>> One patch (http://lists.openfabrics.org/pipermail/general/2009-August/061663.html) checks each 
>> multicast address for validity before it lets it get into the queue. 
> 
> isn't it the below commit which appears in Linus tree?
> 
> Or.
>> commit 5e47596bee12597824a3b5b21e20f80b61e58a35
>> Author: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Yes, thanks you...
I must have missed it.

So there is only one question left. Do we also need the other patch?

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-09-21 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 13:31 How to handle illegal multicast addresses in IPoIB? Moni Shoua
     [not found] ` <4AB78040.9000606-hKgKHo2Ms0F+cjeuK/JdrQ@public.gmane.org>
2009-09-21 14:33   ` Or Gerlitz
     [not found]     ` <4AB78EC9.7020805-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-09-21 14:39       ` Moni Shoua [this message]
     [not found]         ` <4AB7900F.2020406-hKgKHo2Ms0F+cjeuK/JdrQ@public.gmane.org>
2009-09-21 17:08           ` Jason Gunthorpe

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=4AB7900F.2020406@Voltaire.COM \
    --to=monis-hkgkho2ms0f+cjeuk/jdrq@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org \
    --cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.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.