Vlad, please pull from
git://git.openfabrics.org/~ralphc/linux-2.6/.git ofed_kernel_1_5
for the following changes:
commit 2b4ea21146db9d57dc2ac496149f8b047b5b6fa5
Author: Ralph Campbell (QLogic)
Date: Mon Nov 30 14:16:11 2009 -0800
IB/qib: merge latest driver fixes
This patch fi
Ralph Campbell wrote:
Vlad, please pull from
Ralph, Tziporet, any reason not to wait till this core patch is accepted
to the mainline kernel?
Or.
commit 840bbefeda26d21bffae6b7cdc88e981fcfb0a45
Author: Ralph Campbell (QLogic)
Date: Mon Nov 30 14:09:34 2009 -0800
IB/core: allow HCA
No reason not to wait unless it goes beyond OFED-1.5
ship date. I don't think waiting until the last minute
is a good idea. Note that this interface is between ib_qib
and ib_core so if the final form accepted upstream is
different, it can be changed without impact since the kernel
modules are all c
Ralph Campbell wrote:
I don't think this is likely to happen since it fixes Roland's original concern
with exporting struct ib_port
whatever, still its a patch to the core that adds new API, etc, needs to
pass the maintainer acceptance. Its been two weeks since you sent v2, so
a kindly reminde
Or Gerlitz wrote:
> Tziporet, any reason not to wait till this core patch is accepted to the
> mainline kernel?
>
Vlad, Tziporet, any reason not to address my question, silently ignore my
email and just pull this without acking as you usually do, what's the story
behind that?!
Or.
__
Sokolovsky
Cc: Ralph Campbell; ewg@lists.openfabrics.org
Subject: Re: [ewg] [PATCH] IB/qib: latest QIB driver fixes
Or Gerlitz wrote:
Tziporet, any reason not to wait till this core patch is accepted to the
mainline kernel?
Vlad, Tziporet, any reason not to address my question, silently ignore
Tziporet Koren wrote:
> Yes – we are going for RC4 this week and GA on 21-Dec, so we need all changes
> now so
> we can make sure the new commits are passing install in all OSes we support
whatever, why not replying on my note saying this? you (vlad) are
acking every pull request with the except
Or - the agreement in Sonoma was that anything submitted to OFED should
also be in the process of going into the kernel. Because Roland can't
always respond in the time frame required to match the OFED schedule, we
explicitly said it didn't have to be accepted. If it turns out that
there is some ma
Betsy Zeller wrote:
> the agreement in Sonoma was that anything submitted to OFED should
> also be in the process of going into the kernel.
what prevents you from sending a reminder to Roland?
Or.
___
ewg mailing list
ewg@lists.openfabrics.org
http://l
> Or - the agreement in Sonoma was that anything submitted to OFED should
> also be in the process of going into the kernel. Because Roland can't
> always respond in the time frame required to match the OFED schedule, we
> explicitly said it didn't have to be accepted. If it turns out that
>
10 matches
Mail list logo
