linux-kernel - Re: [GIT PULL] pin control bulk changes for v3.13

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, 11 Nov 2013 10:00:53 +0000
From:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"christian.ruppert@...lis.com" <christian.ruppert@...lis.com>
Subject: Re: [GIT PULL] pin control bulk changes for v3.13

On 11/11/2013 03:03 PM, Linus Walleij wrote:
> On Mon, Nov 11, 2013 at 8:54 AM, Vineet Gupta
> <Vineet.Gupta1@...opsys.com> wrote:
>> On 11/11/2013 12:14 PM, Linus Walleij wrote:
>>> - Add the Abilis TB10x pin control driver used on the ARC
>>>   architecture. Also the corresponding GPIO driver is merged
>>>   through this tree, so the ARC has full support for pins
>>>   and GPIOs after this.
>> Only the actual DT changes in arch/arc/plat-tb10x are missing which will require a
>> 2nd pull request for ARC for rc1 which could have been avoided had I bitched about
>> it earlier.
> Actually I think device tree changes - if you mean changes to this platform's
> DTS/DTSI files, should go through the ARC arch tree.

But current workflow is prone to broken bisectability - arch maintainers need to
make sure that the core/driver changes hit mainline before the actual dts/dtsi
files in arch/*

> As the idea is to eventually move the DTS stuff out of the kernel we should
> not try to couple these into the subsystem trees.

IMHO putting the 2 parts in a patch series and routing via the same subsys tree
will not really couple them. I fail to see how u would use the commits in driver/*
(or not use the commits in arch/*) to do the proposed seperation of future.

> Bindings Documentation/devicetree/bindings/* should go through the
> subsystem trees though.

Agreed !

-Vineet


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/