linux-kernel - Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership

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]

Message-ID: <CAL_JsqK0SVS+odf-7ZW6ETS7W8q4ZW1i9WQUGOJuG2Jmyph+-A@mail.gmail.com>
Date:	Mon, 22 Jul 2013 22:27:23 -0500
From:	Rob Herring <robherring2@...il.com>
To:	Jon Loeliger <jdl@....com>
Cc:	Grant Likely <grant.likely@...aro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	devicetree@...r.kernel.org, Ian Campbell <ian.campbell@...rix.com>,
	Pawel Moll <pawel.moll@....com>
Subject: Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership

On Mon, Jul 22, 2013 at 4:36 PM, Jon Loeliger <jdl@....com> wrote:
>>
>> My own selfish desire is to easily separate emails for DT bindings and
>> DT core code. I suppose I could do that with a suffix on my email address.
>
> And I've had the reverse problem:  Sorting out the DTC
> and libfdt patches from the noise. :-)

Noise to you is rock-n-roll to me. ;) It's only going to get harder if
lots of email to devicetree-discuss was getting dropped waiting for
moderator approval.

Yours is the harder problem since there is not really a way to use
kernel MAINTAINERS for dtc. Perhaps the kernel maintainer for dtc
could be "Send Your Patch Upstream <nobody@...here.com>".

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/