From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matti Vaittinen Subject: Re: [PATCH v2 0/6] mfd/regulator/clk: bd71837: ROHM BD71837 PMIC driver Date: Tue, 29 May 2018 11:35:41 +0300 Message-ID: <20180529083541.GA13528@localhost.localdomain> References: <20180528090003.GA8778@localhost.localdomain> <20180529073958.GB4790@dell> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20180529073958.GB4790@dell> Sender: linux-kernel-owner@vger.kernel.org To: Lee Jones Cc: Matti Vaittinen , mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, lgirdwood@gmail.com, broonie@kernel.org, mazziesaccount@gmail.com, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, mikko.mutanen@fi.rohmeurope.com, heikki.haikola@fi.rohmeurope.com List-Id: devicetree@vger.kernel.org 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. Br, Matti Vaittinen