From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752323AbeAZONC (ORCPT ); Fri, 26 Jan 2018 09:13:02 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:55769 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751507AbeAZONA (ORCPT ); Fri, 26 Jan 2018 09:13:00 -0500 X-Google-Smtp-Source: AH8x226+y+miRPLs6xrLtofC4wUAZ9zzQt1kZnYafMf+INOx5/tKg8AY95KZfl0TplxKD2Gf+f7rJQ== Date: Fri, 26 Jan 2018 14:12:55 +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: <20180126141255.7adgqjlonuvujp2x@dell> References: <9c50fe6a-21cc-e49d-1b10-5d2457ed4e2a@users.sourceforge.net> <20180123125851.ysypf7375sjlgsc6@dell> <20180123130130.powyttapsx3djawx@dell> <20180123151419.prwq62c7gpsnpbx3@dell> <20180123163130.h6ygmzig7syafxbh@dell> <49873902-c947-468d-094a-4ac175850116@users.sourceforge.net> <20180126114514.dwhwwgcp4n6fayre@dell> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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: Any more private messages from now on will be ignored. > >> I got other preferences for time ranges around patch distribution. > > > > Not sure what this means. I'm guessing you're saying that you are not > > willing to collect your patches and you intend on sending them one at > > a time, over time. > > You interpreted my feedback in an unwanted direction. > > I am just browsing through the Linux software landscape. > Corresponding patches will evolve according to the varying sizes of > affected directories. > > > > If I am understanding you correctly, then your patches will not > > be reviewed. > > Another review will hopefully happen (under other circumstances). > > > >> When will the adjustments which you could integrate already > >> appear on the Linux next interface? > >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/drivers/mfd/ > > > > When the merge-window closes. > > 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. Are you using Google Translate to convert between your first language and English? 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. Repo: git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git Branch: for-mfd-next-next -- Lee Jones Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog