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:	Tue, 26 Apr 2016 08:35:49 -0500
From:	Rob Herring <robh@...nel.org>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Eric Engestrom <eric@...estrom.ch>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

On Tue, Apr 26, 2016 at 1:35 AM, Lee Jones <lee.jones@...aro.org> wrote:
> On Mon, 25 Apr 2016, Rob Herring wrote:
>
>> On Mon, Apr 25, 2016 at 11:58 AM, Lee Jones <lee.jones@...aro.org> wrote:
>> > On Mon, 25 Apr 2016, Rob Herring wrote:
>> >
>> >> On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
>> >> > Signed-off-by: Eric Engestrom <eric@...estrom.ch>
>> >>
>> >> Applied, thanks.
>> >
>> > I'd prefer to continue taking these if you don't mind Rob.  It'd limit
>> > on the amount of immutable branch pull requests I have to send/handle.
>>
>> Why? Do you really expect to have a dependency here?
>
> Because the file is in ".*/mfd/.*", which normally goes through the MFD
> tree.
>
> $ git log --committer="Rob Herring" --oneline -- Documentation/devicetree/bindings/mfd/ | wc -l
> 6
> $ git log --committer="Lee Jones" --oneline -- Documentation/devicetree/bindings/mfd/ | wc -l
> 99

That is because most changes are coupled with drivers. For changes
that are standalone without any dependency, they go thru my tree. If
we're getting any merge conflicts beyond which Linus can/wants to fix,
then there is a problem because bindings shouldn't be changing that
much.

Eventually, I think we need to merge all the bindings thru a single
tree. Otherwise, we'll never move toward moving bindings out of the
kernel (unless we just sync from the kernel tree to a standalone
repo).

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ