public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: penguin-kernel@I-love.SAKURA.ne.jp, sean.hefty@intel.com,
	opurdila@ixiacom.com, eric.dumazet@gmail.com,
	netdev@vger.kernel.org, nhorman@tuxdriver.com,
	ebiederm@xmission.com, linux-kernel@vger.kernel.org,
	rolandd@cisco.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] rdma/cm: Randomize local port allocation.
Date: Tue, 20 Apr 2010 12:34:25 +0800	[thread overview]
Message-ID: <4BCD2ED1.4080702@redhat.com> (raw)
In-Reply-To: <20100416.133001.262206466.davem@davemloft.net>

David Miller wrote:
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Fri, 16 Apr 2010 22:54:22 +0900
> 
>> Cong Wang wrote:
>>> Sean Hefty wrote:
>>>> I like this version, thanks!  I'm not sure which tree to merge it through.
>>>> Are you needing this for 2.6.34, or is 2.6.35 okay?
>>>>
>>> As soon as possible, so 2.6.34. :)
>>>
>> Cong, merge window for 2.6.34 was already closed.
>> You need to make your patchset towards 2.6.35 (using net-next-2.6 tree)
>> rather than 2.6.34 (using linux-2.6 tree). Therefore, this patch being
>> queued for 2.6.35 (through net-next-2.6 tree) should be okay for you.
> 
> I don't take RDMA patches into net-next-2.6, the less I touch this
> stack avoiding stuff the better and Roland has been taking this stuff
> into his own tree for some time now.

I left for a few days.

Ok, so I will wait for this to be merged.

Thanks, David and Tetsuo!


      reply	other threads:[~2010-04-20  4:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100412100744.5302.92442.sendpatchset@localhost.localdomain>
     [not found] ` <20100412100816.5302.74919.sendpatchset@localhost.localdomain>
     [not found]   ` <201004130121.o3D1Lhh7099571@www262.sakura.ne.jp>
     [not found]     ` <4BC41994.7030707@redhat.com>
     [not found]       ` <4BC42FE0.4040601@redhat.com>
     [not found]         ` <201004132207.GAJ52684.OJFtMQVFHOSFLO@I-love.SAKURA.ne.jp>
     [not found]           ` <21DAC78125424ED291B5D6477CFF9657@amr.corp.intel.com>
     [not found]             ` <201004140201.o3E21Aqn075978@www262.sakura.ne.jp>
     [not found]               ` <195EB1AD388F455AA386EB214FCD09F4@amr.corp.intel.com>
     [not found]                 ` <201004150229.o3F2T4dZ054768@www262.sakura.ne.jp>
     [not found]                   ` <201004150229.o3F2T4dZ054768-etx+eQDEXHD7nzcFbJAaVXf5DAMn2ifp@public.gmane.org>
2010-04-15 19:55                     ` [PATCH] rdma/cm: Randomize local port allocation Sean Hefty
2010-04-16  2:22                       ` Cong Wang
     [not found]                         ` <4BC7C9CF.20403-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-04-16 13:54                           ` Tetsuo Handa
     [not found]                             ` <201004162254.FJF73478.SHOOMOFtQFVJLF-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
2010-04-16 20:30                               ` David Miller
2010-04-20  4:34                                 ` Cong Wang [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=4BCD2ED1.4080702@redhat.com \
    --to=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=opurdila@ixiacom.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rolandd@cisco.com \
    --cc=sean.hefty@intel.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