From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= Date: Thu, 09 Apr 2015 13:11:58 +0000 Subject: Re: [PATCH resend] Renesas Ethernet AVB driver Message-Id: <873849cuox.fsf@nemi.mork.no> List-Id: References: <2926619.fiYHPz1IBk@wasted.cogentembedded.com> <20150328082853.GA4255@localhost.localdomain> <5519D380.6070200@cogentembedded.com> <20150331064349.GB4605@localhost.localdomain> In-Reply-To: <20150331064349.GB4605@localhost.localdomain> (Richard Cochran's message of "Tue, 31 Mar 2015 08:43:49 +0200") MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Richard Cochran Cc: Sergei Shtylyov , robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org, galak@codeaurora.org, netdev@vger.kernel.org, linux-sh@vger.kernel.org, Mitsuhiro Kimura , masaru.nagai.vx@renesas.com, David Miller Richard Cochran writes: > The reason for the author's SOB is to make sure that he or she is > really authorized (like from the employer) to contribute the driver. I believe it is wise to stick to the definition of "Developer's Certificate of Origin 1.1" from SubmittingPatches. Which most definitely allow you to sign off on any GPL licensed code, whether the original author(s) included a SOB tag or not: .. (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or .. Bj=C3=B8rn From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= Subject: Re: [PATCH resend] Renesas Ethernet AVB driver Date: Thu, 09 Apr 2015 15:11:58 +0200 Message-ID: <873849cuox.fsf@nemi.mork.no> References: <2926619.fiYHPz1IBk@wasted.cogentembedded.com> <20150328082853.GA4255@localhost.localdomain> <5519D380.6070200@cogentembedded.com> <20150331064349.GB4605@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Sergei Shtylyov , robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org, galak@codeaurora.org, netdev@vger.kernel.org, linux-sh@vger.kernel.org, Mitsuhiro Kimura , masaru.nagai.vx@renesas.com, David Miller To: Richard Cochran Return-path: Received: from canardo.mork.no ([148.122.252.1]:44234 "EHLO canardo.mork.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755226AbbDINNl convert rfc822-to-8bit (ORCPT ); Thu, 9 Apr 2015 09:13:41 -0400 In-Reply-To: <20150331064349.GB4605@localhost.localdomain> (Richard Cochran's message of "Tue, 31 Mar 2015 08:43:49 +0200") Sender: netdev-owner@vger.kernel.org List-ID: Richard Cochran writes: > The reason for the author's SOB is to make sure that he or she is > really authorized (like from the employer) to contribute the driver. I believe it is wise to stick to the definition of "Developer's Certificate of Origin 1.1" from SubmittingPatches. Which most definitel= y allow you to sign off on any GPL licensed code, whether the original author(s) included a SOB tag or not: =2E. (b) The contribution is based upon previous work that, to the b= est of my knowledge, is covered under an appropriate open sourc= e license and I have the right under that license to submit t= hat work with modifications, whether created in whole or in par= t by me, under the same open source license (unless I am permitted to submit under a different license), as indicate= d in the file; or =2E. Bj=C3=B8rn