From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755511AbaIBWoJ (ORCPT ); Tue, 2 Sep 2014 18:44:09 -0400 Received: from mail-pd0-f175.google.com ([209.85.192.175]:48571 "EHLO mail-pd0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755292AbaIBWoF (ORCPT ); Tue, 2 Sep 2014 18:44:05 -0400 Date: Tue, 2 Sep 2014 15:44:00 -0700 From: Brian Norris To: Florian Fainelli Cc: Olof Johansson , Russell King - ARM Linux , Arnd Bergmann , Matt Porter , Christian Daudt , "linux-arm-kernel@lists.infradead.org" , Linux Kernel , "devicetree@vger.kernel.org" , Gregory Fong , Marc Carino Subject: Re: [PATCH v8 03/11] ARM: brcmstb: add debug UART for earlyprintk support Message-ID: <20140902224400.GY18411@ld-irv-0074> References: <1405976886-27807-1-git-send-email-computersforpeace@gmail.com> <1405976886-27807-4-git-send-email-computersforpeace@gmail.com> <20140802083040.GY30282@n2100.arm.linux.org.uk> <20140804165627.GT3711@ld-irv-0074> <54064323.3090406@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54064323.3090406@gmail.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 On Tue, Sep 02, 2014 at 03:22:27PM -0700, Florian Fainelli wrote: > On 08/13/2014 03:16 PM, Olof Johansson wrote: > > [snip] > > >>>> I noticed that you sent this to the patch system. I asked Olof last > >>>> night whether he had anything in arm-soc touching Kconfig.debug, and > >>>> he does (a number of other platforms have updated it.) This means > >>>> that if I apply it to my tree, it may conflict, so I'm reluctant to > >>>> take it. > >>> > >>> OK... Matt told me that such patches go through you. So which is it? > >>> Should all Kconfig.debug patches go through the arm-soc route? > >> > >> How should this get in? Should I rebase/resend through Matt and > >> arm-soc? Or can you pick this up as-is? > > > > Kconfig.debug is something that we usually merge new platforms for > > through arm-soc. The main exception has been release cycles when > > Russell has been doing major surgery on the file (one of those was a > > few releases ago), where we've backed off to avoid conflicts. > > > > That's been the assumed arrangement from our side at least, we haven't > > had anything more formal than that. > > > > So, go ahead and send it through us -- if we end up having a cycle > > where we can't apply it we can send it over to Russell for you. > > It looks like somehow, this patch got lost somewhere in the submission > process. Is it too late to accept it for 3.17 if we were to re-submit it? I already resubmitted this weeks ago: http://article.gmane.org/gmane.linux.ports.arm.kernel/348468 No comment / action so far. Brian From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Norris Subject: Re: [PATCH v8 03/11] ARM: brcmstb: add debug UART for earlyprintk support Date: Tue, 2 Sep 2014 15:44:00 -0700 Message-ID: <20140902224400.GY18411@ld-irv-0074> References: <1405976886-27807-1-git-send-email-computersforpeace@gmail.com> <1405976886-27807-4-git-send-email-computersforpeace@gmail.com> <20140802083040.GY30282@n2100.arm.linux.org.uk> <20140804165627.GT3711@ld-irv-0074> <54064323.3090406@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <54064323.3090406@gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: Florian Fainelli Cc: Olof Johansson , Russell King - ARM Linux , Arnd Bergmann , Matt Porter , Christian Daudt , "linux-arm-kernel@lists.infradead.org" , Linux Kernel , "devicetree@vger.kernel.org" , Gregory Fong , Marc Carino List-Id: devicetree@vger.kernel.org On Tue, Sep 02, 2014 at 03:22:27PM -0700, Florian Fainelli wrote: > On 08/13/2014 03:16 PM, Olof Johansson wrote: > > [snip] > > >>>> I noticed that you sent this to the patch system. I asked Olof last > >>>> night whether he had anything in arm-soc touching Kconfig.debug, and > >>>> he does (a number of other platforms have updated it.) This means > >>>> that if I apply it to my tree, it may conflict, so I'm reluctant to > >>>> take it. > >>> > >>> OK... Matt told me that such patches go through you. So which is it? > >>> Should all Kconfig.debug patches go through the arm-soc route? > >> > >> How should this get in? Should I rebase/resend through Matt and > >> arm-soc? Or can you pick this up as-is? > > > > Kconfig.debug is something that we usually merge new platforms for > > through arm-soc. The main exception has been release cycles when > > Russell has been doing major surgery on the file (one of those was a > > few releases ago), where we've backed off to avoid conflicts. > > > > That's been the assumed arrangement from our side at least, we haven't > > had anything more formal than that. > > > > So, go ahead and send it through us -- if we end up having a cycle > > where we can't apply it we can send it over to Russell for you. > > It looks like somehow, this patch got lost somewhere in the submission > process. Is it too late to accept it for 3.17 if we were to re-submit it? I already resubmitted this weeks ago: http://article.gmane.org/gmane.linux.ports.arm.kernel/348468 No comment / action so far. Brian From mboxrd@z Thu Jan 1 00:00:00 1970 From: computersforpeace@gmail.com (Brian Norris) Date: Tue, 2 Sep 2014 15:44:00 -0700 Subject: [PATCH v8 03/11] ARM: brcmstb: add debug UART for earlyprintk support In-Reply-To: <54064323.3090406@gmail.com> References: <1405976886-27807-1-git-send-email-computersforpeace@gmail.com> <1405976886-27807-4-git-send-email-computersforpeace@gmail.com> <20140802083040.GY30282@n2100.arm.linux.org.uk> <20140804165627.GT3711@ld-irv-0074> <54064323.3090406@gmail.com> Message-ID: <20140902224400.GY18411@ld-irv-0074> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Sep 02, 2014 at 03:22:27PM -0700, Florian Fainelli wrote: > On 08/13/2014 03:16 PM, Olof Johansson wrote: > > [snip] > > >>>> I noticed that you sent this to the patch system. I asked Olof last > >>>> night whether he had anything in arm-soc touching Kconfig.debug, and > >>>> he does (a number of other platforms have updated it.) This means > >>>> that if I apply it to my tree, it may conflict, so I'm reluctant to > >>>> take it. > >>> > >>> OK... Matt told me that such patches go through you. So which is it? > >>> Should all Kconfig.debug patches go through the arm-soc route? > >> > >> How should this get in? Should I rebase/resend through Matt and > >> arm-soc? Or can you pick this up as-is? > > > > Kconfig.debug is something that we usually merge new platforms for > > through arm-soc. The main exception has been release cycles when > > Russell has been doing major surgery on the file (one of those was a > > few releases ago), where we've backed off to avoid conflicts. > > > > That's been the assumed arrangement from our side at least, we haven't > > had anything more formal than that. > > > > So, go ahead and send it through us -- if we end up having a cycle > > where we can't apply it we can send it over to Russell for you. > > It looks like somehow, this patch got lost somewhere in the submission > process. Is it too late to accept it for 3.17 if we were to re-submit it? I already resubmitted this weeks ago: http://article.gmane.org/gmane.linux.ports.arm.kernel/348468 No comment / action so far. Brian