linux-kernel - Re: [PATCH v2 0/6] mfd/regulator/clk: bd71837: ROHM BD71837 PMIC driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180529083541.GA13528@localhost.localdomain>
Date:   Tue, 29 May 2018 11:35:41 +0300
From:   Matti Vaittinen <mazziesaccount@...il.com>
To:     Lee Jones <lee.jones@...aro.org>
Cc:     Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        mturquette@...libre.com, sboyd@...nel.org, robh+dt@...nel.org,
        mark.rutland@....com, lgirdwood@...il.com, broonie@...nel.org,
        mazziesaccount@...il.com, linux-clk@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        mikko.mutanen@...rohmeurope.com, heikki.haikola@...rohmeurope.com
Subject: Re: [PATCH v2 0/6] mfd/regulator/clk: bd71837: ROHM BD71837 PMIC
 driver

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