linux-kernel - Re: [PATCH V2 1/2] dt-bindings: regulator: Add document for MT6323 regulator

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]

Date:	Mon, 25 Jan 2016 13:05:52 +0100
From:	John Crispin <blogic@...nwrt.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	devicetree@...r.kernel.org, Steven Liu <steven.liu@...iatek.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	Henry Chen <henryc.chen@...iatek.com>,
	linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
	Matthias Brugger <matthias.bgg@...il.com>,
	Chen Zhong <chen.zhong@...iatek.com>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH V2 1/2] dt-bindings: regulator: Add document for MT6323
 regulator



On 25/01/2016 12:37, Mark Brown wrote:
> On Mon, Jan 25, 2016 at 11:40:04AM +0100, John Crispin wrote:
>> Based on the MT6397 binding documentation.
>>
>> Signed-off-by: John Crispin <blogic@...nwrt.org>
>> Cc: devicetree@...r.kernel.org
> 
> In reply to your previous submission I said:
> 
> | important.  Please also use subject lines matching the style for the
> | subsystem (for patch 1).
> 
> Please don't ignore review comments, people are generally making them
> for a reason and are likely to have the same concerns if issues remain
> unaddressed.  Having to repeat the same comments can get repetitive and
> make people question the value of time spent reviewing.  If you disagree
> with the review comments that's fine but you need to reply and discuss
> your concerns so that the reviewer can understand your decisions.
> 

Hi,

sorry about that. I've been juggling with a pile of patches the last
couple of weeks and missed folding the fixup into the patch before
sending it. I've just sent you a V3.

	John