From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MALFORMED_FREEMAIL, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D4A16C3524A for ; Tue, 4 Feb 2020 05:08:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ABA8B21582 for ; Tue, 4 Feb 2020 05:08:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="cb9WOLeP" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726506AbgBDFIl (ORCPT ); Tue, 4 Feb 2020 00:08:41 -0500 Received: from mail-ed1-f66.google.com ([209.85.208.66]:38780 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726151AbgBDFIk (ORCPT ); Tue, 4 Feb 2020 00:08:40 -0500 Received: by mail-ed1-f66.google.com with SMTP id p23so18521778edr.5; Mon, 03 Feb 2020 21:08:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=EOehpKBxDkbplUHN6oDL4a2sNVmEAPe8+ZU2b8kq5Yo=; b=cb9WOLeP5FuhT+WSH3fZo7yVOwmSEkUU+WUl0U+QAZNVT3Z5XdGG+Bd6i4+15QVQos E1lxfeu9mYXTdM8di/7y7IzCkRSwWcbGlmkU5B57vKNY7rYJRdfQTL7jpOxSov1/AzUG aUALIieobGYIv0aR/43Y7cOtQo9YNpz419S82WUwc3iavuqjJ1THo6LEDu8TLPxed/tK eOvueH10iOAzGT/oRG3xghvhuUk8zxaCcYPv9tODbWbFBSa44My+sCNqOWHfyRtR3n+0 ynME1U2PkW4lasqOr2twbjtpzw8uCR45YwuGChUtFE2uswwipeaNNByJkdgfur6dITqR N9/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=EOehpKBxDkbplUHN6oDL4a2sNVmEAPe8+ZU2b8kq5Yo=; b=JGPT7yBMNfRTRqUxc/0ezvqp3n8kLV6G0W75zpaDeRrVlY7EpZcU7hveezveYO+HZI CkQ6maoIEcMb0C7XmRAWCIn/UjdcEFFKnW4p8bFgE92ZkfqBA7QcqR37q3/soO3ZICf7 2xydmnl27Md1ehZ8j4Aby032zJ2x7tFpBi7mEhfk4dkc+dTFT8Q4BL+p/rAPzFRGAkQS ASgXdrthWEZTpKCi2NUP40h5bjsB7oBZFfrbmgOSrnOVxipFuAcbieR+WwNFpgCfyO/W Nz5UJePyPqlVIig+P5fISzXHQynrKsAn46956CvjJitw/1dqeL5LcUa+7MLHzB9DPV7I a/Qg== X-Gm-Message-State: APjAAAUIAoYNAQLF4pTHuJCM8VkNgO4HLSNPT0Nf0BDsV9JOXmHdjaTw ftgj3WqqaxgiE0qQtnVI9JQ= X-Google-Smtp-Source: APXvYqxMOWCMu+l63Kvc5ncOkddOLlTa4A+kMAU7qeSxUkXNiXg8pvV1fEfQ++nMb34HBVbIN0bXLw== X-Received: by 2002:a17:906:7d6:: with SMTP id m22mr24019635ejc.335.1580792918983; Mon, 03 Feb 2020 21:08:38 -0800 (PST) Received: from felia ([2001:16b8:2daa:dc00:2c0a:8928:125e:2b0f]) by smtp.gmail.com with ESMTPSA id j17sm1132429ejo.1.2020.02.03.21.08.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 03 Feb 2020 21:08:38 -0800 (PST) From: Lukas Bulwahn X-Google-Original-From: Lukas Bulwahn Date: Tue, 4 Feb 2020 06:08:37 +0100 (CET) X-X-Sender: lukas@felia To: Andy Shevchenko cc: Joe Perches , Jakub Kicinski , Lukas Bulwahn , Karsten Keil , Arnd Bergmann , isdn4linux@listserv.isdn4linux.de, netdev , Linux Kernel Mailing List Subject: Re: [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section In-Reply-To: Message-ID: References: <20200201124301.21148-1-lukas.bulwahn@gmail.com> <20200202124306.54bcabea@cakuba.hsd1.ca.comcast.net> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, 3 Feb 2020, Andy Shevchenko wrote: > On Mon, Feb 3, 2020 at 1:08 PM Joe Perches wrote: > > On Mon, 2020-02-03 at 12:13 +0200, Andy Shevchenko wrote: > > > On Sun, Feb 2, 2020 at 10:45 PM Jakub Kicinski wrote: > > ... > > > > I'm not sure it's ready. I think parse-maintainers.pl will change few > > > lines here. > > > > parse-maintainers would change a _lot_ of the MAINTAINERS file > > by reordering section letters. > > I think it's quite easy to find out if it had changed the record in question. > I checked it and it does change a bit. My patch adds to a list of file entries sorted by "relevance" (not alphabetically) two further minor (by relevance) entries, i.e., Kconfig and Makefile, to the end of that list. The other reorderings would have already applied to the original state; rather than trying to "fix" this locally for this one patch here, I would prefer to understand why the discussion on splitting the MAINTAINERS file, summarized at https://lwn.net/Articles/730509/, got stuck and how I can contribute to that. If that bigger change would happen, we could automatically clean up all the entries when the things are splitted, rather than sending reordering patches to the maintainers that then spend time on trying to merge that all back together. Lukas