From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932133AbcIEA6z (ORCPT ); Sun, 4 Sep 2016 20:58:55 -0400 Received: from ozlabs.org ([103.22.144.67]:35016 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754146AbcIEA6x (ORCPT ); Sun, 4 Sep 2016 20:58:53 -0400 Date: Mon, 5 Sep 2016 10:58:03 +1000 From: Stephen Rothwell To: Olof Johansson , Arnd Bergmann , ARM Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Russell King , "David S. Miller" , Linus Walleij Subject: linux-next: manual merge of the arm-soc tree with Linus' tree Message-ID: <20160905105803.13ed27ff@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 arm-soc tree got a conflict in: arch/arm/mach-realview/core.c between commit: 2fb04fdf3019 ("net: smc91x: fix SMC accesses") from Linus' tree and commit: 7484c727b636 ("ARM: realview: delete the RealView board files") from the arm-soc tree. I fixed it up (I deleted the file) 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