[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FFEC9CE.3000306@mellanox.com>
Date: Thu, 12 Jul 2012 15:57:50 +0300
From: Hadar Hen Zion <hadarh@...lanox.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: David Miller <davem@...emloft.net>, <netdev@...r.kernel.org>,
<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Hadar Hen Zion <hadarh@...lanox.co.il>,
Or Gerlitz <ogerlitz@...lanox.com>,
Jack Morgenstein <jackm@....mellanox.co.il>,
Roland Dreier <roland@...nel.org>, <linux-rdma@...r.kernel.org>
Subject: Re: linux-next: manual merge of the net-next tree with the infiniband
tree
On 7/12/2012 5:13 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in
> include/linux/mlx4/device.h between commit 396f2feb05d7 ("mlx4_core:
> Implement mechanism for reserved Q_Keys") from the infiniband tree and
> commit 0ff1fb654bec ("{NET, IB}/mlx4: Add device managed flow steering
> firmware API") from the net-next tree.
>
> Just context changes. I fixed it up (see below) and can carry the fix
> as necessary.
>
Thanks Stephen.
Please add:
Acked-by: Hadar Hen Zion <hadarh@...lanox.co.il>
Hadar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists