linux-kernel - Re: [PATCH] MAINTAINERS: Don't send to devicetree list for "arch/*/boot/dts"

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] [day] [month] [year] [list]

Message-ID: <CAL_JsqJgtr_Z9H9Z3OJGnbD9asqYKdeziFKP--VRxh=7Qi3bVQ@mail.gmail.com>
Date:	Thu, 24 Oct 2013 05:40:12 -0500
From:	Rob Herring <robherring2@...il.com>
To:	Mauro Carvalho Chehab <m.chehab@...sung.com>
Cc:	Doug Anderson <dianders@...omium.org>,
	Grant Likely <grant.likely@...aro.org>,
	Rob Herring <rob.herring@...xeda.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Cesar Eduardo Barros <cesarb@...arb.net>,
	Joe Perches <joe@...ches.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Don't send to devicetree list for "arch/*/boot/dts"

On Wed, Oct 23, 2013 at 5:54 PM, Mauro Carvalho Chehab
<m.chehab@...sung.com> wrote:
> Em Wed, 23 Oct 2013 12:12:32 -0500
> Rob Herring <robherring2@...il.com> escreveu:
>
>> On 10/23/2013 08:22 AM, Doug Anderson wrote:
>> > As discussed in the ARM kernel summit, people on the devicetree list
>> > would no longer like to receive emails about all dts changes.  Remove
>> > from MAINTAINERS.
>>
>> We need to make sure platform maintainers are copied though. That may be
>> hard since we don't have standard layout/naming of dts files.
>>
>> We might also want to drop these:
>> K:      of_get_property
>> K:      of_match_table
>>
>> They are at least on the wrong maintainer list now as they should be
>> associated with the binding maintainers and not DT core code if we do
>> keep them.
>>
>> Also based on the discussion, we need to add
>> Documentation/devicetree/bindings/* to appropriate subsystem
>> maintainers, but that should probably wait until after Friday at least.
>
> /me is confused. What's the procedure for the DT patches for the devices
> supported by the subsystem I maintain, e. g. patches for
> /drivers/media/platform?
>
> Should I just apply them, if I think that it is needed by the hardware?
> Are there any criteria to be followed? If so, what criteria?
>
> /me hopes that all those questions will be discussed/answered at KS on
> Friday's discussions ;)

Yes, it should all become clear at the DT slot on Fri.

> In any case, my suggestion is that this patch should be a way more verbose,
> and should come together with a patch adding something at Documentation
> (SubmittingPatches, or maybe SubmitingDTPatches) in order to be sure that
> both developers and subsystem maintainers will do the right thing.

A binding howto/best practices doc is planned which should help in this area.

Rob
--
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/