> PATCHv6 is the latest version. Should we use it?
> http://lists.openfabrics.org/pipermail/general/2008-December/055727.html
OK, so I just tried to apply this, but I'm not sure what tree it's
against. For example, I see this in patch 1/2:
> --- a/drivers/infiniband/core/addr.c
> +++ b/drivers/infiniband/core/addr.c
> @@ -43,6 +43,7 @@
> #include <net/netevent.h>
> #include <net/addrconf.h>
> #include <rdma/ib_addr.h>
> +#include <net/ip6_route.h>
but the includes in the kernel look like
#include <net/neighbour.h>
#include <net/route.h>
#include <net/netevent.h>
#include <rdma/ib_addr.h>
and as far as I can tell they haven't changed for a long time. And
further down the patch, I see
> -static int addr_resolve_remote(struct sockaddr *src_in,
> - struct sockaddr *dst_in,
but again my kernel looks different:
static int addr_resolve_remote(struct sockaddr_in *src_in,
struct sockaddr_in *dst_in,
and again that code hasn't changed in several years.
rather than having me continuing to try and fix this up by hand (and
probably break something), can you resend the series with the patches
regenerated against an unpatched kernel? Best is Linus's tree, but
really this area hasn't changed for a long time so pretty much and
kernel should do.
Thanks.
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
