Roland,

I just recalled that once the 3.2 merge window opens Dave is going to
push that drivers/net separation change done by Jeff K. which moves
drivers/net/mlx4 to drivers/net/ethernet/mellanox/mlx4 see
https://github.com/davem330/net-next/tree/master/drivers/net/ethernet/mellanox/mlx4
- is this going to introduce problem with mlx4 patches you gonna push
from your net-next or the git creature can pass that safely? if
there's an issue here, what would be the correct method to resolve
that? maybe wait a day or two for Dave's pull request and the actual
pull by Linus and then rebase the infiniband/for-next tree/branch on a
snapshot of Linus tree and then send a pull request?

Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to