Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751098AbdCQMCv (ORCPT ); Fri, 17 Mar 2017 08:02:51 -0400 Received: from mail-it0-f67.google.com ([209.85.214.67]:33679 "EHLO mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750898AbdCQMCt (ORCPT ); Fri, 17 Mar 2017 08:02:49 -0400 MIME-Version: 1.0 In-Reply-To: <20170313130138.GV11350@io.lakedaemon.net> References: <1489324627-19126-1-git-send-email-geert@linux-m68k.org> <1489324627-19126-6-git-send-email-geert@linux-m68k.org> <20170313130138.GV11350@io.lakedaemon.net> From: Geert Uytterhoeven Date: Fri, 17 Mar 2017 13:02:26 +0100 X-Google-Sender-Auth: vTCbIxDD4xRlq3RkyBv70YW1Aio Message-ID: Subject: Re: [PATCH v2 05/23] MAINTAINERS: Add file patterns for dove device tree bindings To: Jason Cooper Cc: "devicetree@vger.kernel.org" , Rob Herring , Mark Rutland , "linux-kernel@vger.kernel.org" , Andrew Lunn , Sebastian Hesselbarth , Gregory Clement , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3418 Lines: 75 Hi Jason, On Mon, Mar 13, 2017 at 2:01 PM, Jason Cooper wrote: > On Sun, Mar 12, 2017 at 02:16:49PM +0100, Geert Uytterhoeven wrote: >> Submitters of device tree binding documentation may forget to CC >> the subsystem maintainer if this is missing. >> >> Signed-off-by: Geert Uytterhoeven >> Cc: Jason Cooper >> Cc: Andrew Lunn >> Cc: Sebastian Hesselbarth >> Cc: Gregory Clement >> Cc: linux-arm-kernel@lists.infradead.org >> --- >> Please apply this patch directly if you want to be involved in device >> tree binding documentation for your subsystem. >> >> v2: >> - No changes. >> >> Impact on next-20170310: >> >> +Jason Cooper (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support) >> +Andrew Lunn (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support) >> +Sebastian Hesselbarth (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support) >> +Gregory Clement (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support) >> Rob Herring (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) >> Mark Rutland (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) >> +linux-arm-kernel@lists.infradead.org (moderated list:ARM/Marvell Dove/MV78xx0/Orion SOC support) >> devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) >> linux-kernel@vger.kernel.org (open list) >> --- >> MAINTAINERS | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index 6428d3c82fce9670..ce461fefec6c9463 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -1486,6 +1486,7 @@ M: Sebastian Hesselbarth >> M: Gregory Clement >> L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers) >> S: Maintained >> +F: Documentation/devicetree/bindings/soc/dove/ > > I'm not opposed to the idea, but I'm not seeing how we can do this > completely. What you've added only covers dove soc bindings. There's > orion5x, kirkwood, and all the newer mvebu socs. Not to mention a lot > of IP blocks we care about that aren't SoC- or Marvell-specific. There's no orion5x, kirkwood, mvebu, ... under Documentation/devicetree/bindings/soc. > The dts files have a much more clear file pattern -> maintainer pairing. > Perhaps we should make checkpatch smarter? e.g. compatible strings > found in changed binding docs are searched for in dts{i} files. Hits > are mapped to maintainers. The DTS files are maintained by a platform maintainer, while my patch series was about Linux kernel subsystem maintainers. In this particular case both maintainers are the same, but this is not true in general. Hence deriving a platform maintainer from a Linux subsystem specific binding document is the wrong way around. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds