From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757867AbcHWKLU (ORCPT ); Tue, 23 Aug 2016 06:11:20 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:58701 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757789AbcHWKKx (ORCPT ); Tue, 23 Aug 2016 06:10:53 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Mark Rutland , Ian Campbell , devicetree@vger.kernel.org, Stephen Warren , Catalin Marinas , Lee Jones , Will Deacon , linux-kernel@vger.kernel.org, Rob Herring , Eric Anholt , arm@kernel.org, Gerd Hoffmann , Frank Rowand , linux-rpi-kernel@lists.infradead.org Subject: Re: [PATCH v2 1/2] ARM: dts: Remove use of skeleton.dtsi from bcm283x.dtsi Date: Tue, 23 Aug 2016 12:09:52 +0200 Message-ID: <7746678.0mZLVD2k0J@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-31-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: <20160818102349.GC27045@leverpostej> References: <1470233565-30154-1-git-send-email-ijc@hellion.org.uk> <1471504916.6295.32.camel@hellion.org.uk> <20160818102349.GC27045@leverpostej> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:CorKRZJIsbGWhS/lWqgbnAcXL3LBXth2QcHxXNkDOpGMmsEWzKb wj/LzrMYLduWxERJrWtIuww/E2gD3f8EcDL1x1rkxJwP/m3skIhNqNZA4eiX2KTZ4dMp0It Dc8zbYNt72wb2A/7QUeKfDr/kX6u1ptu7PcdCsvN7PPq5O9QB6hVQOPPVn1WYg0hgkq5fzG evjO2qMcSiVZIMxWPX6Mg== X-UI-Out-Filterresults: notjunk:1;V01:K0:RBbe//zciVU=:o4VtO+tLt2X9u7+uGTo+jY jJY/zubXHWm+KOcr39WTxif/PUuMfv0fUD5Vj/aoqm1lrcMrU1QSFulG5G+NX768twWWDBnrT CJ6FHmMlFLoMSH+bti7YLspzJDFuVrJeoQv+eGf34dz/fdbJQRicaEDe2FtLKHB4bKBO/6jOa 9MvCzydyv1q/E+NRlGWXZ4aXGycbqXZgwksDTqfGNWPler259BFb8XNPT3enD64rKu/ekKfYQ ryuS3EuyTffrLMwn7giywZkEKZIJ3mUikmC+dL8FTdz5y7/+NNniN363l6Komnj4Ao7KrMUfb uNTRCT6SmvHnbrsX8dWyBsqKHvZdW6AFrj7JhSLlBIEPxA25llsWsdDkIebvrMGyEcuccsQak 3xnCOAJ8oGSl90qpZ8tDFNBwnNkNVDSCRtuCno2fdKRMAwDiQgd1GjbAtmu33cDCd3miHeOhg PbekrkbFoQAGEBm4CVLEbFdNj5sh4bTbUHErU1INjWgCmkd/QDBvy8kV3NnCt9zdOOsAxYVG/ RYJNFax47EQc41EwDF1mBhSGqHZGDvK0G4V7A/B5Pp8CKm13lKKJt4eZOv1uAHfzOffXBI1Rf TWQ0Rtkuo0OCU2Ke1y5VnnDJ4Zyn1PIXE3LeicyYA2YzbxJo3GaQhZn/ZnL0wC4RcbqFlalLp A650MkrgSgnJGJthZTwoxk9lhGOKDu6K/GYTOg0eHYLh9/HpkBMmbBtQf/O4G6z4hdm9l/Zgr gpwEd71MKnqJR7l0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, August 18, 2016 11:23:49 AM CEST Mark Rutland wrote: > On Thu, Aug 18, 2016 at 08:21:56AM +0100, Ian Campbell wrote: > > On Tue, 2016-08-09 at 11:48 +0100, Ian Campbell wrote: > > > On Wed, 2016-08-03 at 15:48 +0100, Mark Rutland wrote: > > > > > > > > > [...]Signed-off-by: Ian Campbell > > > > > > > > I also don't have the relevant hardware to test with, but this > > > looks > > > > generally like the right thing. So FWIW: > > > > > > > > Acked-by: Mark Rutland > > > > > > Thanks (and Stefan too). > > > > > > I think these things generally go via the arm-soc tree? Arnd & Olaf, > > > would it be possible to get this fix in for rc2 please (or in any event > > > for 4.8). Although it's an external tree I believe build breakage in > > > the split-out DT git repo is worth addressing. > > > > This change doesn't appear to be in either v4.8-rc2, Linus' tree nor in > > the arm-soc tree that I can see. So, ping? > > > > Or am I barking up the wrong tree pointing this patch towards arm-soc > > (via arm@k.o)? > > That's the right place. > > The best thing to do would be to resend the patch, with all tags > accumulated, with arm-soc, Arnd, and Olof in the To line (rather than > Cc'd), so it's clear they need to action it. I had skipped the new message as well while sorting through 5000 messages after my vacation, but I've now put it into my TODO folder and will get to it eventually. We sometimes miss stuff that is meant for arm-soc when it comes from people that don't normally send us patches. If you want to be sure to catch the attention, stick a 'GIT PULL' into the subject or send a ping on IRC. The easiest way for us is when things get funnelled through the platform maintainers that handle all the other patches, but I can see how that may be annoying for a patch like this. Arnd