Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752622AbaBES4p (ORCPT ); Wed, 5 Feb 2014 13:56:45 -0500 Received: from mail-we0-f169.google.com ([74.125.82.169]:41761 "EHLO mail-we0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751047AbaBES4n (ORCPT ); Wed, 5 Feb 2014 13:56:43 -0500 MIME-Version: 1.0 In-Reply-To: References: <1391463780-19840-1-git-send-email-markus.mayer@linaro.org> Date: Wed, 5 Feb 2014 10:56:42 -0800 Message-ID: Subject: Re: [PATCH] gpio: bcm281xx: Update MODULE_AUTHOR From: Markus Mayer To: Linus Walleij Cc: bcm-kernel-feedback-list , Alexandre Courbot , Linux GPIO List , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5 February 2014 02:03, Linus Walleij wrote: > On Mon, Feb 3, 2014 at 10:43 PM, Markus Mayer wrote: > >> Add Broadcom's upstreaming mailing list address to MODULE_AUTHOR. >> >> Signed-off-by: Markus Mayer > > Hm OK not that this is used very much, and nothing to argue about > so patch applied. Thanks. I am hopefully done the trivial changes to this driver now. > 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. That's exactly right. > 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! I'll talk to Christian about this and see what we can come up with. Regards, -Markus -- Markus Mayer Broadcom Landing Team -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/