From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> To: David Miller <davem@davemloft.net>, richardcochran@gmail.com Cc: 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.kc@renesas.com, masaru.nagai.vx@renesas.com Subject: Re: [PATCH resend] Renesas Ethernet AVB driver Date: Tue, 31 Mar 2015 17:40:34 +0000 [thread overview] Message-ID: <551ADC12.5050603@cogentembedded.com> (raw) In-Reply-To: <20150331.113832.2042398685489897677.davem@davemloft.net> Hello. On 03/31/2015 06:38 PM, David Miller wrote: >>>> We also need SOB from Mitsuhiro and Masaru. >>> Hmm, it's the first time I encounter such requirement. >> I think this is normal policy. I have seen it more than once on lkml. >> 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. We (Cogent Embedded) are authorized to do this, isn't this enough? >> [adding davem on CC] >> Dave, is that correct? > I refuse to apply any patch without an appropriate signoff. But what do you mean by "appropriate signoff"? I have provided mine but Richard insists there should be sign-offs from the primary driver authors -- it's the first time I'm encountering such a requirement. WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> To: David Miller <davem@davemloft.net>, richardcochran@gmail.com Cc: 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.kc@renesas.com, masaru.nagai.vx@renesas.com Subject: Re: [PATCH resend] Renesas Ethernet AVB driver Date: Tue, 31 Mar 2015 20:40:34 +0300 [thread overview] Message-ID: <551ADC12.5050603@cogentembedded.com> (raw) In-Reply-To: <20150331.113832.2042398685489897677.davem@davemloft.net> Hello. On 03/31/2015 06:38 PM, David Miller wrote: >>>> We also need SOB from Mitsuhiro and Masaru. >>> Hmm, it's the first time I encounter such requirement. >> I think this is normal policy. I have seen it more than once on lkml. >> 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. We (Cogent Embedded) are authorized to do this, isn't this enough? >> [adding davem on CC] >> Dave, is that correct? > I refuse to apply any patch without an appropriate signoff. But what do you mean by "appropriate signoff"? I have provided mine but Richard insists there should be sign-offs from the primary driver authors -- it's the first time I'm encountering such a requirement. WBR, Sergei
next prev parent reply other threads:[~2015-03-31 17:40 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-27 23:13 [PATCH resend] Renesas Ethernet AVB driver Sergei Shtylyov 2015-03-27 23:13 ` Sergei Shtylyov 2015-03-28 5:17 ` Lino Sanfilippo 2015-03-28 5:17 ` Lino Sanfilippo 2015-03-28 8:36 ` Richard Cochran 2015-03-28 8:36 ` Richard Cochran 2015-03-28 13:55 ` Sergei Shtylyov 2015-03-28 13:55 ` Sergei Shtylyov 2015-03-28 8:28 ` Richard Cochran 2015-03-28 8:28 ` Richard Cochran 2015-03-28 18:26 ` David Miller 2015-03-28 18:26 ` David Miller 2015-03-30 22:51 ` Sergei Shtylyov 2015-03-30 22:51 ` Sergei Shtylyov 2015-03-31 6:43 ` Richard Cochran 2015-03-31 6:43 ` Richard Cochran 2015-03-31 9:01 ` Richard Cochran 2015-03-31 9:01 ` Richard Cochran 2015-03-31 15:38 ` David Miller 2015-03-31 15:38 ` David Miller 2015-03-31 17:40 ` Sergei Shtylyov [this message] 2015-03-31 17:40 ` Sergei Shtylyov 2015-03-31 17:48 ` David Miller 2015-03-31 17:48 ` David Miller 2015-04-03 6:27 ` masaru.nagai.vx 2015-04-03 6:27 ` masaru.nagai.vx 2015-04-03 6:27 ` masaru.nagai.vx 2015-04-12 22:03 ` Sergei Shtylyov 2015-04-12 22:03 ` Sergei Shtylyov 2015-04-09 13:11 ` Bjørn Mork 2015-04-09 13:11 ` Bjørn Mork 2015-04-09 17:57 ` David Miller 2015-04-09 17:57 ` David Miller 2015-04-13 20:23 ` Sergei Shtylyov 2015-04-13 20:23 ` Sergei Shtylyov 2015-04-14 5:27 ` Richard Cochran 2015-04-14 5:27 ` Richard Cochran 2015-04-14 10:14 ` Sergei Shtylyov 2015-04-14 10:14 ` Sergei Shtylyov 2015-04-14 16:30 ` Richard Cochran 2015-04-14 16:30 ` Richard Cochran 2015-04-14 16:58 ` Sergei Shtylyov 2015-04-14 16:58 ` Sergei Shtylyov 2015-04-14 18:30 ` Richard Cochran 2015-04-14 18:30 ` Richard Cochran 2015-04-15 1:01 ` masaru.nagai.vx 2015-04-15 1:01 ` masaru.nagai.vx 2015-04-15 1:01 ` masaru.nagai.vx 2015-04-15 5:31 ` Richard Cochran 2015-04-15 5:31 ` Richard Cochran 2015-04-02 13:56 ` Ben Hutchings 2015-04-02 13:56 ` Ben Hutchings 2015-04-13 20:34 ` Sergei Shtylyov 2015-04-13 20:34 ` Sergei Shtylyov 2015-04-13 22:13 ` Lino Sanfilippo 2015-04-13 22:13 ` Lino Sanfilippo 2015-04-13 22:31 ` Ben Hutchings 2015-04-13 22:31 ` Ben Hutchings 2015-04-13 22:53 ` Lino Sanfilippo 2015-04-13 22:53 ` Lino Sanfilippo 2015-04-13 23:08 ` Ben Hutchings 2015-04-13 23:08 ` Ben Hutchings
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=551ADC12.5050603@cogentembedded.com \ --to=sergei.shtylyov@cogentembedded.com \ --cc=davem@davemloft.net \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=ijc+devicetree@hellion.org.uk \ --cc=linux-sh@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=masaru.nagai.vx@renesas.com \ --cc=mitsuhiro.kimura.kc@renesas.com \ --cc=netdev@vger.kernel.org \ --cc=pawel.moll@arm.com \ --cc=richardcochran@gmail.com \ --cc=robh+dt@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.