Received: by 10.223.176.46 with SMTP id f43csp4376883wra; Tue, 23 Jan 2018 08:32:43 -0800 (PST) X-Google-Smtp-Source: AH8x2261vXGf5HAm7ORHUMsKQI3o9ZrSOux3N6i9Fg+S2E05x+V5KQhmKa8N49o+/R3cXqL1lW+X X-Received: by 10.157.20.211 with SMTP id r19mr7874268otr.107.1516725162883; Tue, 23 Jan 2018 08:32:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516725162; cv=none; d=google.com; s=arc-20160816; b=PyqjpbKbSevpFU1rS1rryd0qOnwyE3SjTDPtV+FOD0wn3roJAvBdOLlXbcfmmOiiaM jQTDbqz7sRZ/rKA7EFRRVRx+B/55YJhx0C2WhTe/AWH8qut0E1kkVkvAQ+om9WTDFTR4 OhRwlJxzoZ0iE723BRUno52peD4shVRCMmfPnSgGgWpClsAovxuYuyxYq2M5MonHa6ft WrNf5Zjy9K51W8wYDyBC2eZFxaGOPMnGI1IZZcPUjfaqiym+R3MFqZy3cf0tPBEYYDjt XKTRPa54Apmk6Ko4WiiZGdBxgJlapRrsHSYvq+eFdALXo1XG8spnIHyAoqWHE6f/zSU0 9/DQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=uA5e17C+qan9hPoh8EsAozEzPAuko5zGx/9XWWdHbsg=; b=DKXNVe8b7UF7EMQ+sT4tgH4s2uw/qhffB5SMO3i1fmcrz1S3g2OMJ6qWD/cw0w5Qp1 YTIjGTsYG5MXp4q6izg5EBZTbEZtmFIwmkFjwbLoXEVEcvleRYqv5uWMraMLLswcT4Qq ufLAF0hNLyhTChC7CibRPRMebzV9a4yrisxuRMFqmBAFLhnxwj9CYayAnK4krUDu5zg3 MDKyF2jCjk7aDIeHf/zwWbsxv7F50Ja7W4MjpUidzv2qZI/Kjt1SxLlVpuJfp201yV2b pny8Rg6pjZEkXs6NI+hUmTZXRabcgj84ebHaWZa38MNyDapLcEJUOz5JAnMSKBY22Cw+ vUnA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=OZitVaSy; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j198si8599027ite.30.2018.01.23.08.32.29; Tue, 23 Jan 2018 08:32:42 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=OZitVaSy; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751607AbeAWQbh (ORCPT + 99 others); Tue, 23 Jan 2018 11:31:37 -0500 Received: from mail-wm0-f44.google.com ([74.125.82.44]:44161 "EHLO mail-wm0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751256AbeAWQbf (ORCPT ); Tue, 23 Jan 2018 11:31:35 -0500 Received: by mail-wm0-f44.google.com with SMTP id t74so3035598wme.3 for ; Tue, 23 Jan 2018 08:31:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=uA5e17C+qan9hPoh8EsAozEzPAuko5zGx/9XWWdHbsg=; b=OZitVaSyglVgnnImWfXGSVlWnR69rI3Xjazi6BTxdlzzR9VHHDqiQnwpIpgzlgQ3ci ka/U7NLbXSCrYRIzv6rUlHWPD4LKrlLJ3TZYYr9AbJrhIODpOj9/LiebqrbJDgEjlzo0 bd/KNJ74AWjdHhI6XN6ZH4Z8qEHuTk1KbbIGo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=uA5e17C+qan9hPoh8EsAozEzPAuko5zGx/9XWWdHbsg=; b=aimMu6ipRwuoy1BNRiG9ukCgYWt865PUqUUJW4H/i/IfCZakyN18bwp2mgT1gpJl5U DO21ns6ygoB+UPlGGsL7wrZ6ZusMdJkWTV9v0DEuME7stldMHPHxcM0/gSvcqOhSMu9I NUBiqLB2sfL77C91qOMmgAuYZDor2ElOAGWUXloZ3y8QaetypJp4sMVqH0F+mPLhS17E NLno7Ai0CjRVdVqwpUQDed+PYsp6DZmDwccnD9lcwXts1iItk6CxwURI9h/Sv5h0VfYG 549kqQecadSYdhy37xtb5Y0jqr2BeySZRlJP6d042UHBo9eoLhpKkKhyhyhgN4UB8IVp +ntA== X-Gm-Message-State: AKwxyteKokJeHmvoJq9OIp953r/Tz5WnrgcrVu8H6PhUX6wGCv19KTmx sq2cNfCeECn+YQJBwwjT5DWlUQ== X-Received: by 10.28.168.8 with SMTP id r8mr2582487wme.157.1516725093991; Tue, 23 Jan 2018 08:31:33 -0800 (PST) Received: from dell ([2.27.167.60]) by smtp.gmail.com with ESMTPSA id l41sm1120279wrl.1.2018.01.23.08.31.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 23 Jan 2018 08:31:32 -0800 (PST) Date: Tue, 23 Jan 2018 16:31:30 +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: <20180123163130.h6ygmzig7syafxbh@dell> References: <9c50fe6a-21cc-e49d-1b10-5d2457ed4e2a@users.sourceforge.net> <20180123125851.ysypf7375sjlgsc6@dell> <20180123130130.powyttapsx3djawx@dell> <20180123151419.prwq62c7gpsnpbx3@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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 23 Jan 2018, SF Markus Elfring wrote: > > My preferred mailer (Mutt) re-orders replied-to mails by putting them > > to the top of my Inbox. At which point I have to re-navigate down to > > the next patch to review. > > How much does this tool influence the amount of update suggestions > which you could handle easily and safely? In the 5 years I've been doing this, this is the first time someone has submitted in such a way as to cause an issue. > > This is fine for most submissions, but you have fired ~30, > > mostly individual patches at me. > > This number could be appropriate. I tried to contribute hundreds > of change possibilities for various software components. Moving forward, my advice to you would be to collect grouped patches on a number of topic branches, then send them out in batches, perhaps every couple of weeks. Sending ~30 patches individually, spaced over a few hours/days, is actually not a good system. It is in fact quite inappropriate and a pain to manage. I for one find many (to be fair, very trivial) patches scatter-gunned throughout my inbox to be rather inconvenient. What I should do really is ask you to take all similar (remove error message, don't use sizeof(struct X), remove '== NULL') changes and squash them into single patches. However, I realise that you might want the "upstream creds", so I won't do that -- but not at the expense of my time/effort. The two choices are to squash or to create a set. > > I'd like you to do the following please: > > It will take a while until you might get the next chance to take > another look at these subsequent patches. I'm not in a hurry. -- Lee Jones Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog