Remember that kernels after the release of 3.0 but before 3.1-rc1 will report their version as 3.0 (even though they may have lots of commits that went in after the 3.0 release). Could that be the explanation?
On Tue, Aug 16, 2011 at 3:34 AM, Bernd Schubert <[email protected]> wrote: > Hello Erez, > > are you sure? Commit 69cce1d1404968f78b177a0314f5822d5afdbbfb is not in 3.0 > yet and I also don't see how 3.0 should fail there, as it tests immediately > for "if (likely(skb_dst(skb)" > > > Thanks, > Bernd > > On 08/16/2011 10:06 AM, Erez Shitrit wrote: >> >> Hi, >> it happened in 3.0 also, if you take the git tag v3.0-rc7 and below it >> will work. >> >> Thanks, Erez -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
