From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751397AbeA2JfO (ORCPT ); Mon, 29 Jan 2018 04:35:14 -0500 Received: from mail-wr0-f179.google.com ([209.85.128.179]:37190 "EHLO mail-wr0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751162AbeA2JfL (ORCPT ); Mon, 29 Jan 2018 04:35:11 -0500 X-Google-Smtp-Source: AH8x2251SE6zLc3RtaZ00hdUWcVniu+yuod41CJ/NccwkxvnYltRy/ipaiHcJT5IUERT7Njm8XR15A== Date: Mon, 29 Jan 2018 09:35:08 +0000 From: Lee Jones To: SF Markus Elfring Cc: kernel-janitors@vger.kernel.org, LKML , Lars =?iso-8859-1?Q?P=F6schel?= , Samuel Ortiz Subject: Re: mfd: Patch management? Message-ID: <20180129093507.huxiai5yjbvg7vkf@dell> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <856e9b19-2e42-a6b2-85c4-c89a81b071f8@users.sourceforge.net> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 26 Jan 2018, SF Markus Elfring wrote: > >> I am curious if more positive feedback could evolve till then. > >> I would appreciate if a potentially needed resend for my selection > >> of update suggestions could become smaller (when reviewed steps > >> could be already integrated for example). > > > > I'm not entirely sure what you're trying to say, > > in any of your responses. > > 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. You can't 'go around' me, if that's what you're thinking. > > If you want to rebase your patches, to see what has been applied and > > what hasn't, you can use the MFD repo and its next-next branch. > > https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/log/?h=for-mfd-next-next > > 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, I've kindly requested that you gather all of your MFD patches and send them as one single set. Is there a good reason why you're not willing to do so? -- Lee Jones Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog