From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751802Ab2GPIbR (ORCPT ); Mon, 16 Jul 2012 04:31:17 -0400 Received: from mail-ee0-f46.google.com ([74.125.83.46]:36386 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751736Ab2GPIbO (ORCPT ); Mon, 16 Jul 2012 04:31:14 -0400 From: Jack Morgenstein Organization: Mellanox To: Stephen Rothwell Subject: Re: linux-next: manual merge of the net-next tree with the infiniband tree Date: Mon, 16 Jul 2012 11:34:34 +0300 User-Agent: KMail/1.9.1 Cc: David Miller , netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Hadar Hen Zion , Or Gerlitz , Roland Dreier , linux-rdma@vger.kernel.org References: <20120712121307.a482863a98848e3813690ef2@canb.auug.org.au> In-Reply-To: <20120712121307.a482863a98848e3813690ef2@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201207161134.34574.jackm@dev.mellanox.co.il> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 12 July 2012 05:13, 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! Your merge looks fine. Ack. -Jack