Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754608AbcDNJjz (ORCPT ); Thu, 14 Apr 2016 05:39:55 -0400 Received: from mail-wm0-f53.google.com ([74.125.82.53]:38668 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753651AbcDNJju (ORCPT ); Thu, 14 Apr 2016 05:39:50 -0400 Date: Thu, 14 Apr 2016 11:39:45 +0200 From: Daniel Lezcano To: Vladimir Murzin Cc: arnd@arndb.de, linux@arm.linux.org.uk, gregkh@linuxfoundation.org, tglx@linutronix.de, liviu.dudau@arm.com, sudeep.holla@arm.com, lorenzo.pieralisi@arm.com, mark.rutland@arm.com, gnomes@lxorguk.ukuu.org.uk, peter@hurleysoftware.com, pawel.moll@arm.com, ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com, robh+dt@kernel.org, linux-serial@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System Message-ID: <20160414093945.GA15250@linaro.org> References: <1459519381-34441-1-git-send-email-vladimir.murzin@arm.com> <570F593D.6040809@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <570F593D.6040809@arm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 922 Lines: 28 On Thu, Apr 14, 2016 at 09:47:57AM +0100, Vladimir Murzin wrote: > Hi, > > On 01/04/16 15:02, Vladimir Murzin wrote: > > Hi, > > > > This patch series provides the basic support for running ucLinux on V2M-MPS2 > > platform. > > > > With these patches applied ucLinux can be run on both HW and FVP models > > with Cortex-M3/M4/M7 configurations. > > Any objection to get it merged? > > Sudeep Holla noticed that there is merge conflict against linux-next > with PIC32 uart (Makefile and serial_core.h), so should I provide > conflict resolution or do rebase on someone's branch? > > Anyway, I'd be glad to know how it should be processed further? This patchset should go through the arm-soc tree. Any conflicts resulting from a merge *after* your patchset is in the arm-soc tree is no longer your problem. So IOW, if your patchset applies to arm-soc and Arnd is ok to pick it, then everything is fine. -- Daniel