Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp312661imm; Thu, 31 May 2018 00:28:11 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJU+RtsZjs/cwCI6Muo/agxA0M0KaFcB14iXE71w0BpHW4t6PRqyx1hcw2IjQmxtJAeOT0a X-Received: by 2002:a62:da59:: with SMTP id w25-v6mr1187158pfl.161.1527751691886; Thu, 31 May 2018 00:28:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527751691; cv=none; d=google.com; s=arc-20160816; b=rVYztoxV5cuAE5xGGebVV/j3jYZRvQPr4QZ6J9W+78leTdQMys9aDdT8zdijb/CkIl jm3ZOPDsdg6QNDZHJhLUAkM2WFoyl1f7tU/eFm8Xo9etoXG0xA+WQdnINCMe8vHt9NgQ +6bL7gp7Zb62xF2OfEw/Hvlj5KP7ej7HYdAIJrOAjnY2RzncclslGE5o45I7wIxo/akX +EBDYBmei18VedYac3hHgyq+/YWDFv284bm06384G2ivIZFgZvUz9jAsaYOcsY/Eltei 1pLhoBIKG2hiQU4xUkPeqbKh7pTv0/jNn16zAhQHexEKSmzFwclCzU1b516sYnsodtrE pxLQ== 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-disposition:mime-version:references:message-id:subject:cc :to:date:from:dkim-signature:arc-authentication-results; bh=X513GlQeiF9U7ddTHDZNvtT9Br0hndUWfQIvuxczTO4=; b=hMofHdOPYQ/g+C64OaTt5WThL8z7/8LAuYNhDplR+k+7N52T7gBRQxlYzhYr3V65Ym pABZMffy5vbd61DuniTJipyQO5LbQv2/1PycADSJwusIOC1Kx8gHmWkjbeREX/lQFm45 +ZCQjE2ghtCAm4+chcRDz+7i4l6A6PeiBkwu6zNRlX9RvHvjUA8xu1RnNqXrmAGlbPqB QYFNPKtF5+dUA0JqDRFfFovv5xI/6Vj4Btjip5tPQMjS++Cqk2ynfQT8vi0WYDjc8gzb /FmCAyBrHZR2UcijWe/4G9jtncpmFtkHtV7JpC8I46enn/f2A/hoZRpUcnpRghw762te ra/Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=B4Xnav7/; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v73-v6si7608941pfi.22.2018.05.31.00.27.57; Thu, 31 May 2018 00:28:11 -0700 (PDT) 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=@gmail.com header.s=20161025 header.b=B4Xnav7/; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754038AbeEaH1I (ORCPT + 99 others); Thu, 31 May 2018 03:27:08 -0400 Received: from mail-lf0-f66.google.com ([209.85.215.66]:35819 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753846AbeEaH1E (ORCPT ); Thu, 31 May 2018 03:27:04 -0400 Received: by mail-lf0-f66.google.com with SMTP id y72-v6so8199817lfd.2; Thu, 31 May 2018 00:27:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=X513GlQeiF9U7ddTHDZNvtT9Br0hndUWfQIvuxczTO4=; b=B4Xnav7/qLn4ZF8BD0XLohQbhf7S5feR1OJ6YjgAb9DIPCnpx592AyX5jRQ4JH1nqg n2SaFB01XhLqrvxbAOARLavRNFAcVxNHZ5pD17kZtlL20d4wLOJS7qh9KHi8fZ6cyy19 BJ7+x2MQSdLv3F856ZyX1t2yhfnaxxmgvyeBFSLsRe0pg2GgO8dTgJvkjsZnq4ssaMFk A2KDsnOlDDM3TSwlCx8YMKsWV5g9o5HyilAzF0/7etWbhxqfapHg12ZmJaxK85zzhqZj 7nbl52aEgQMwZO5tmaavCZodUOsNdaNfW1yrLSBNexq1ypdhlcFAabHnAZf6SBNde7tW s8FA== 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:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=X513GlQeiF9U7ddTHDZNvtT9Br0hndUWfQIvuxczTO4=; b=CQXhtHOrDZQV2wP7xJaPFQcdXL7jN+6dbQKDRoqspPKmHmPf+2GSAfUvJHcKy5k3JD yswYqIfXW4E4MlgQCmP4wtIHz8IwenD1pYvXI7H/l3izdCI9q+4S9OxYx4O0uM32pz6/ tfujAidXQDAYUjLtjYRsP6XGaOzCOeZ1wZFDKfWOxjTl/3wK1osfEzR9vyt+ZP3J4HI5 rnkkM+D828V6Rt5dprwE/r5dXq1fA8TjpU2ZtotzY5/AU7YBKhharQdjn6gYsIz+iab0 wOYntxbyIOnPRjO2gpkCPUWZnVCcW+HncUKySP18lHddJ1+Tc7FvJHIjTjBP98V4YOAR 39vQ== X-Gm-Message-State: ALKqPwd9E3c1hMRiyWjbheXgp0GbmrU8yVjWw/0xQfhqKI13G82QyQjM g8P4MoQrI4wtDYUMGxKrDJ8= X-Received: by 2002:a19:9c4b:: with SMTP id f72-v6mr3758342lfe.119.1527751623265; Thu, 31 May 2018 00:27:03 -0700 (PDT) Received: from localhost.localdomain ([213.255.186.34]) by smtp.gmail.com with ESMTPSA id j15-v6sm7461422lji.89.2018.05.31.00.27.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 31 May 2018 00:27:02 -0700 (PDT) From: Matti Vaittinen X-Google-Original-From: Matti Vaittinen Date: Thu, 31 May 2018 10:26:59 +0300 To: Stephen Boyd Cc: Lee Jones , Matti Vaittinen , Matti Vaittinen , mturquette@baylibre.com, robh+dt@kernel.org, mark.rutland@arm.com, lgirdwood@gmail.com, broonie@kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, mikko.mutanen@fi.rohmeurope.com, heikki.haikola@fi.rohmeurope.com Subject: Re: [PATCH v2 0/6] mfd/regulator/clk: bd71837: ROHM BD71837 PMIC driver Message-ID: <20180531072659.GI13528@localhost.localdomain> References: <20180528090003.GA8778@localhost.localdomain> <20180529073958.GB4790@dell> <20180529083541.GA13528@localhost.localdomain> <20180530111649.GB8038@dell> <152769382760.144038.10609724773770264610@swboyd.mtv.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <152769382760.144038.10609724773770264610@swboyd.mtv.corp.google.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 30, 2018 at 08:23:47AM -0700, Stephen Boyd wrote: > Quoting Lee Jones (2018-05-30 04:16:49) > > On Tue, 29 May 2018, Matti Vaittinen wrote: > > > > > Hello, > > > > > > On Tue, May 29, 2018 at 08:39:58AM +0100, Lee Jones wrote: > > > > On Mon, 28 May 2018, Matti Vaittinen wrote: > > > > > > > > > Patch series adding support for ROHM BD71837 PMIC. > > > > FYI, this patch-set is going to be difficult to manage since it was > > > > not sent 'threaded'. > > > > > > > > If/when you send a subsequent version, could you please ensure you > > > > send the set threaded so the patches keep in relation to one another > > > > as they are reviewed? > > > > > > Thanks for the guidance. I have not sent so many patches to community so > > > I am grateful also from all the practical tips =) Just one slight problem. > > > I have only seen emails being threaded when one is replying to an email. > > > So how should I send my patches in same thread? Just send first one and > > > then send subsequent patches as replies? > > > > > > I just killed some unused definitions and one unused variable from the > > > code so I am about to send new version. I'll try doing that as a threaded > > > series and resend all the patches as v3. > > > > You don't need to do this manually. > > > > Just use `git send-email` with the correct arguments. > > > > I usually send with 'git send-email *.patch' so that git can do the > threading for me. Looks like these patches were sent with Mutt though, > so perhaps 'git format-patch | git imap-send' was used without the > --thread option on format-patch. Yep. I used git format-patch without the --thread and mutt -H for sending. Learned the --thread after Lee pointed out the threading and used it for further series. Thanks for the help! Br, Matti Vaittinen