Re: [PATCH 02/22] Firmware interface code for IB device.

[Roland Dreier <rdreier@cisco.com>]

    Greg> Yes, that doesn't matter.  But it seems that the svn tree is
    Greg> vastly different from the in-kernel code.  So much so that
    Greg> some companies feel that the in-kernel stuff just isn't
    Greg> worth running at all.

I don't want to belabor this issue... but the svn tree is not vastly
different than what's in the kernel.  It has some things that aren't
upstream yet, and which are important to some people.  For example,
the IBM ehca driver we're talking about, as well as the PathScale
driver, SDP (sockets direct protocol), etc.  It just takes time for
this new code to get to the point where both the developers of the new
stuff feel it's ready to be merged, and the kernel community agrees
that it should be merged.

    Greg> Yes, that does make me happy.  But it doesn't make me happy
    Greg> to see IBM not being able to participate in kernel
    Greg> development by posting and defending their own code to lkml.
    Greg> I thought IBM knew better than that...

Agreed.  But let's not get sidetracked on that internal IBM issue.
The ehca developers have assured me that they can and will participate
in the thread reviewing their driver.  It seems like it's better for
me to help them work around their internal problems by acting as a
proxy, than for me to delay merging their driver just because someone
in IBM management is clueless.

 - R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/