linux-kernel - Re: [PATCH] gpio: bcm281xx: Update MODULE

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: <CACRpkda=h=0bpMfHeq-zJs5nZ+740rz9jZChCk0OAHm=Jmw5AQ@mail.gmail.com>
Date:	Wed, 5 Feb 2014 11:03:32 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Markus Mayer <markus.mayer@...aro.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>
Cc:	Alexandre Courbot <gnurou@...il.com>,
	Linux GPIO List <linux-gpio@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpio: bcm281xx: Update MODULE_AUTHOR

On Mon, Feb 3, 2014 at 10:43 PM, Markus Mayer <markus.mayer@...aro.org> wrote:

> Add Broadcom's upstreaming mailing list address to MODULE_AUTHOR.
>
> Signed-off-by: Markus Mayer <markus.mayer@...aro.org>

Hm OK not that this is used very much, and nothing to argue about
so patch applied.

However we do not really recognize corporate bodies as maintainers,
only physical people whose GPG keys we can sign ... but I
guess you wanted to convey that the driver is the work of several
individuals inside BRCM and thus authors, while you take care
of the maintenance.

A patch to MAINTAINERS adding this to Christians entry for
the SoCs or as a standalone entry with Markus as maintainer
would be more important and usefule than this though, so I'm
throwing out that challenge!

Yours,
Linus Walleij
--
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/