Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932116Ab2BWOcH (ORCPT ); Thu, 23 Feb 2012 09:32:07 -0500 Received: from moutng.kundenserver.de ([212.227.17.8]:49602 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755227Ab2BWOcE (ORCPT ); Thu, 23 Feb 2012 09:32:04 -0500 From: Arnd Bergmann To: "Ohad Ben-Cohen" Subject: Re: [GIT PULL] adding rpmsg and remoteproc to 3.4 Date: Thu, 23 Feb 2012 14:31:44 +0000 User-Agent: KMail/1.12.2 (Linux/3.3.0-rc1; KDE/4.3.2; x86_64; ; ) Cc: linux-kernel@vger.kernel.org, "linux-arm" , linux-omap@vger.kernel.org, "Grosen, Mark" , Brian Swetland , Grant Likely , Tony Lindgren , Rusty Russell , Greg KH , akpm@linux-foundation.org, Stephen Boyd , Russell King , "Shah, Bhavin" , Iliyan Malchev , "Anna, Suman" , "Guzman Lugo, Fernando" , Stephen Rothwell , Loic PALLARDY , Linus Walleij , Ludovic BARRE , Michal Simek , "Clark, Rob" , John Williams , Saravana Kannan , arm@kernel.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201202231431.44497.arnd@arndb.de> X-Provags-ID: V02:K0:Icxh52v5VCzlFksfiG9z0jcm0IKbKQ3XYzb+tfaGjPr SxNWyDGnaIf+TG3wGlSRtACf+F+i70AkVMrzOlaYQnEY++/ion NwQuh8VIAbRBbHjN9+f9kl8hcnf2erlOh3fX6aJE3s/b5x9G2T tcbzC6by6FXr+SsavmuTFeP2zKEM6Da/M7NtB88T7rMBrkW/jI gINhjjUC+apCHgcGo+vtD7wAdt1swsTLPyH4Eg3zBoHaHc+sL9 YO0tn+xFBnA9C8e254SfwXiswU7aXdv3V0XDmShSyMvvumfaMx SwjlBJQxjdD1GNHiByFReQazmFzOskhezTZ1zs2hCHwXaVzQyS jNVEO5ZX5dp9FzRdQh0o= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1473 Lines: 38 On Wednesday 22 February 2012, Ohad Ben-Cohen wrote: > > Hi Arnd, > > Please pull: > > git://git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git rpmsg-for-3.4 > > To get the very basic rpmsg+remoteproc core functionality for 3.4. > > This is basically the same stuff I sent for 3.3, with an additional > fix and cleanup which were reported by Grant (and of course the two > patches that fixed the 3.3 merge conflicts). > > This entire patch set has been sitting in linux-next for quite some > time. I'm not sure if it'd conflict with your tree when you pull it, > but I can of course ask Stephen to remove my tree if things look ok to > you. Hi Ohad, I've looked at the code again now and pulled it into the arm-soc tree as the next/rpmsg branch, queued for submission to Linus in the 3.4 merge window. There won't be any conflicts in linux-next because the commits are identical, so it doesn't matter whether you leave your branch in linux-next or now. If you have updates on top of this branch, I can apply them directly here. Let's see how things go after v3.4-rc1 before we decide whether you want to keep sending patches to arm-soc for v3.5 as well or whether you just use your own branch then. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/