netdev - Re: [PATCH 0/5] ks8851 DT updates

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:	Fri, 23 May 2014 15:37:36 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	sboyd@...eaurora.org
Cc:	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, netdev@...r.kernel.org,
	robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	devicetree@...r.kernel.org, nm@...com
Subject: Re: [PATCH 0/5] ks8851 DT updates

From: Stephen Boyd <sboyd@...eaurora.org>
Date: Fri, 23 May 2014 12:34:01 -0700

> On 05/23/14 12:15, David Miller wrote:
>> From: Stephen Boyd <sboyd@...eaurora.org>
>> Date: Thu, 22 May 2014 14:00:08 -0700
>>
>>> This set of patches properly documents the micrel ks8851 spi ethernet
>>> controller, converts to devm_regulator_get_optional() to make error
>>> paths slightly simpler, and finally adds supports for another
>>> optional regulator and a reset gpio.
>> Please do not submit patch sets that you expect different trees to
>> integrate, this is painful for maintainers to deal with.
>>
>> Instead, submit the changes separately.  One series for one
>> maintainer's tree, another for the other maintainer's tree.
>>
> 
> Ok. Shall I resend this series with the proper separation? Or can you
> ignore the first patch? There isn't any functional dependency, more just
> a checkpatch dependency which is not really all that important.

To avoid all ambiguity please resubmit the new series.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html