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

[Roland Dreier <rdreier@cisco.com>]

    Greg> Checking stuff into a private svn tree is vastly different
    Greg> from posting to lkml in public.  In fact, it looks like the
    Greg> svn tree is so far ahead of the in-kernel stuff, that most
    Greg> people are just using it instead of the in-kernel code.

It's not a private svn tree -- the IBM ehca development is available
to anyone via svn at https://openib.org/svn/gen2/trunk/src/linux-kernel/infiniband/hw/ehca

    Greg> I know at least one company has asked a distro to just
    Greg> accept the svn snapshot over the in-kernel IB code, which
    Greg> makes me wonder if the in-kernel stuff is even useful to
    Greg> people?  Why have it, if companies insist on using the
    Greg> out-of-tree stuff instead?

The IB driver stack is still in its early stages, so although I'm
pushing for things to be merged as fast as possible, the unfortunate
fact is that lots of things that people want to use (including the IBM
ehca driver) are not upstream and are not ready to go upstream yet.
But that doesn't mean we should give up on merging them.

Distro politics are just distro politics -- and there will always be
pressure on distros to ship stuff that's not upstream yet.

 - 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/