From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751567AbeA2KP7 (ORCPT ); Mon, 29 Jan 2018 05:15:59 -0500 Received: from mout.web.de ([212.227.15.14]:54084 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750913AbeA2KP5 (ORCPT ); Mon, 29 Jan 2018 05:15:57 -0500 Subject: Re: mfd: Patch management? To: Lee Jones , kernel-janitors@vger.kernel.org Cc: LKML , =?UTF-8?Q?Lars_P=c3=b6schel?= , Linus Walleij , Samuel Ortiz References: <20180123130130.powyttapsx3djawx@dell> <20180123151419.prwq62c7gpsnpbx3@dell> <20180123163130.h6ygmzig7syafxbh@dell> <49873902-c947-468d-094a-4ac175850116@users.sourceforge.net> <20180126114514.dwhwwgcp4n6fayre@dell> <20180126141255.7adgqjlonuvujp2x@dell> <856e9b19-2e42-a6b2-85c4-c89a81b071f8@users.sourceforge.net> <20180129093507.huxiai5yjbvg7vkf@dell> From: SF Markus Elfring Message-ID: Date: Mon, 29 Jan 2018 11:15:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180129093507.huxiai5yjbvg7vkf@dell> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:UuLuxTB7Un8Gk0Kpxuoc3FI7hdTkdQhJmoivqJ4WN8Bs8cEiWF6 Gwk38ZbG9DNW+mKyKVA4+7vYZEyPEyHsLhO7fF2huFQ8VcZIEuPBQGgBl4EVLdySR9zZ+87 bt+ujjGX/+HlPiGQ+WYqjBfClepfUjFUYd8R+XZSXzAcBW9J9HAyC3Rqmjw5X+rQDAjGaeK T9GA2o4l8H7D/mWwEVyrA== X-UI-Out-Filterresults: notjunk:1;V01:K0:3pXilrU8Lbs=:itGII53BiiGBxWLbf3c5o6 BOt/W4sNY5Je9e5vd1BKhteRqSkFaNG+GNJungQ5IfPzVrnUorkHuGFrqo6eJSH+4eIhOPKn7 0BIB7BRrr6jn3QEzHPE2VshHLc4NyshC67v6ibdxEZXCG5oc2vfQzpLYUxRVWhqP9abxrBpFv stdvzVVzZitmHp2H34RAZjceqzNozImAKMt0W3w5lldEktB+4QnqfKcCzmY5kL6zFDb1NWygI 1OxuPjvCn2XIZdbdOlZ+okePGWnqh+qKamYaQRbp3bX1gVtG/l1hgnFRCMpsDIIy8eeLCvBlD QQhY07ocFs1zJfmun5RR7bti7n4niyaidMdWN3iP5hnyYj66XtLnCZp28J2/HWutSOxqKQ4CV Jrr9hU6NO9HuQe8aoyv1mVkkEz78KocpXimH/55HZT2YksgZgBTSqrLONo0HdIYu6Popni2io 7ysAWef+4OzlkCAkf4ygM3jfAQ0BqhC1ltodZZluHIKKhaGDoezWemUrLHJ7HuPV8YYeC249+ EZExofUqELV7XUgySJabPshdIEXLIs+bJ/FcJk45Kz1jLeiYiC0bnt/0OPRGMDF8KzN1b/rlr eFkNobZACZEOcEN5VxLUlMAE+W6gWTeEpj7NfmwwgnTyWbA6gyTbrsm99uRr3DAX+PR9OAexz 3nQ+ukJdE8O8cmYTPL/9cdHA4dcu9kHtBbQTH9BpFM9SMq6j5Lu5YdlEBJFkah9qA6pTr/hKp c/nnmLGm2f+7u+RZeGM72n1i+gF9px4KwD+/OuFgSvVACe0GQrjQL7KNTdZvRCsVXhxyy3/Li oveP3VRwak/UmHCsb/LlTkT1xkvyGkemxqJCCI3cU5UzmLhZy0= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> I imagine that acceptance for these changes could be influenced >> also by review comments from other contributors. > > Influenced yes, but I will also need to review them. Yes. - This is the usual process. > You can't 'go around' me, if that's what you're thinking. I do not think this. - I hope somehow that additional review comments (by other contributors) could make the handling of shown update candidates more promising. >> How are the chances that further update suggestions will be integrated >> just because I sent them as small patch series in the threaded way? >> >> Examples: >> * tps65910: Adjustments for four function implementations >> https://lkml.org/lkml/2018/1/16/313 >> >> * abx500-core: Adjustments for eight function implementations >> https://lkml.org/lkml/2018/1/16/186 > > In order to not make my life difficult, There are more options to make it a bit easier, aren't there? > I've kindly requested that you gather all of your MFD patches Or the remaining ones …? > and send them as one single set. Do you still insist to get these seven update steps in a bigger patch series despite of their threaded structure? > Is there a good reason why you're not willing to do so? I am trying to find out if a few formal details are really hindering progress on the clarification of affected implementation details. I assume that additional hints could occur until I might rebase mentioned change combinations on another recent commit. Regards, Markus