From: Or Gerlitz <ogerlitz@voltaire.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Roland Dreier <rdreier@cisco.com>,
general@lists.openfabrics.org
Subject: [ofa-general] Re: InfiniBand/RDMA merge plans for 2.6.27
Date: Thu, 17 Jul 2008 10:31:47 +0300 [thread overview]
Message-ID: <487EF563.9090102@voltaire.com> (raw)
In-Reply-To: <ada8ww5jbaf.fsf@cisco.com>
Roland Dreier wrote:
> ... 2.6.26 is already out, so it's time to review what my plans are for the merge window opens.
>
> Core:
>
> - I'm waiting to merge the RDMA_CM_EVENT_ADDR_CHANGE changes that
> depend on core networking changes until such changes are upstream.
> Or, please remind me when that happens.
Dave,
There are some rdma patches for 2.6.27 which are dependent on few
networking patches (below), so Roland can't push them before the net
changes gets in, such that enough time has to be left for the rdma push
before the merge window closes...
Or.
> commit 01f3109de49a889db8adf9116449727547ee497e
> Author: Or Gerlitz <ogerlitz@voltaire.com>
> Date: Fri Jun 13 18:12:02 2008 -0700
>
> bonding: deliver netdev event for fail-over under the active-backup mode
>
> commit 709f8a45e8521f2f4229e5fdf3ded1fb77e2ca4e
> Author: Or Gerlitz <ogerlitz@voltaire.com>
> Date: Fri Jun 13 18:12:01 2008 -0700
>
> bonding: bond_change_active_slave() cleanup under active-backup
>
> commit c1da4ac752b8b0411791d26c678fcf23d2eed242
> Author: Or Gerlitz <ogerlitz@voltaire.com>
> Date: Fri Jun 13 18:12:00 2008 -0700
>
> net/core: add NETDEV_BONDING_FAILOVER event
next parent reply other threads:[~2008-07-17 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ada8ww5jbaf.fsf@cisco.com>
2008-07-17 7:31 ` Or Gerlitz [this message]
2008-07-17 7:37 ` [ofa-general] Re: InfiniBand/RDMA merge plans for 2.6.27 David Miller
2008-07-17 7:44 ` Or Gerlitz
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=487EF563.9090102@voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=davem@davemloft.net \
--cc=general@lists.openfabrics.org \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.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).