From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752983AbdKIJpd (ORCPT ); Thu, 9 Nov 2017 04:45:33 -0500 Received: from mail-lf0-f54.google.com ([209.85.215.54]:56804 "EHLO mail-lf0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752195AbdKIJpb (ORCPT ); Thu, 9 Nov 2017 04:45:31 -0500 X-Google-Smtp-Source: ABhQp+R+h5JUO++2wyYk3E3HDO+rUW2KyO3rUheiNoDkA19XZ2m/72v/j4WjHinFTOsPMLnOgfVJug== From: Daniel Lezcano Subject: Legal question: Author, Sign-off, Company Copyright and gmail To: Linus Torvalds , Greg Kroah-Hartman , Linux Kernel Mailing List Message-ID: <084f9151-523e-a212-bf27-d4a4c23878e4@linaro.org> Date: Thu, 9 Nov 2017 10:45:27 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, I noticed a practice when the patches are submitted where I'm a bit confused about how it fits with the DCO. People are creating gmail accounts to send patches on behalf of their company because the company's email configuration does not allow to send patches or adds extra infos, or whatever... That ends up with patches submitted by a gmail account with no history and verifiable origin and new files containing a company copyright [1]. At the first glance I would say, it is not allowed, and if a company is willing to do opensource, it should provide the tools to its employees to do so. But I don't want block patch submission if this practice is tolerated. What is the policy in this case ? Thanks in advance. -- Daniel [1] https://patchwork.kernel.org/patch/10045815/ -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog