From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751452AbcGRBwZ (ORCPT ); Sun, 17 Jul 2016 21:52:25 -0400 Received: from ozlabs.org ([103.22.144.67]:52129 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751326AbcGRBwY (ORCPT ); Sun, 17 Jul 2016 21:52:24 -0400 Date: Mon, 18 Jul 2016 11:52:21 +1000 From: Stephen Rothwell To: David Miller , Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Florian Fainelli , Raghu Vatsavayi , Derek Chickles , Satanand Burla , Felix Manlunas Subject: linux-next: manual merge of the net-next tree with the net tree Message-ID: <20160718115221.15f719de@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/cavium/liquidio/lio_main.c between commit: 8e6ce7ebeb34 ("net: cavium: liquidio: Avoid dma_unmap_single on uninitialized ndata") from the net tree and commit: 6a885b60dad2 ("liquidio: Introduce new octeon2/3 header") from the net-next tree. I am not sure how to fix this up, so I effectively reverted the net tree commit. Please let me know if something else should be done. I fixed it up (see above) and can carry the fix as necessary. This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: linux-next: manual merge of the net-next tree with the net tree Date: Mon, 18 Jul 2016 11:52:21 +1000 Message-ID: <20160718115221.15f719de@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from ozlabs.org ([103.22.144.67]:52129 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751326AbcGRBwY (ORCPT ); Sun, 17 Jul 2016 21:52:24 -0400 Sender: linux-next-owner@vger.kernel.org List-ID: To: David Miller , netdev@vger.kernel.org Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Florian Fainelli , Raghu Vatsavayi , Derek Chickles , Satanand Burla , Felix Manlunas Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/cavium/liquidio/lio_main.c between commit: 8e6ce7ebeb34 ("net: cavium: liquidio: Avoid dma_unmap_single on uninitialized ndata") from the net tree and commit: 6a885b60dad2 ("liquidio: Introduce new octeon2/3 header") from the net-next tree. I am not sure how to fix this up, so I effectively reverted the net tree commit. Please let me know if something else should be done. I fixed it up (see above) and can carry the fix as necessary. This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell