devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: masaru.nagai.vx@renesas.com, davem@davemloft.net
Cc: richardcochran@gmail.com, 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
Subject: Re: [PATCH resend] Renesas Ethernet AVB driver
Date: Mon, 13 Apr 2015 01:03:16 +0300	[thread overview]
Message-ID: <552AEBA4.405@cogentembedded.com> (raw)
In-Reply-To: <551E32E2.3020102@renesas.com>

Hello.

On 04/03/2015 09:27 AM, masaru.nagai.vx@renesas.com wrote:

>> From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Date: Tue, 31 Mar 2015 20:40:34 +0300
> ...
>> Is there a serious problem getting the original authors to signoff on
>> this driver submission?  If so, why?  This should be very
>> straightforward, and if for some reason these authors are unwilling to
>> then I have every reason to be concerned about this.

> We are already agree on the work by sergei.
> So, this patch does not have problem.

    Actually, it does, and not even a single one. :-)

> Sergei, please append SOB of us to this patch.

    Thank you, will add to the new version.

> Signed-off-by: Mitsuhiro Kimura <mitsuhiro.kimura.kc@renesas.com>
> Signed-off-by: Masaru Nagai <masaru.nagai.vx@renesas.com>

> Best Regards,
> Masaru Nagai

WBR, Sergei


  reply	other threads:[~2015-04-12 22:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 23:13 [PATCH resend] Renesas Ethernet AVB driver Sergei Shtylyov
2015-03-28  5:17 ` Lino Sanfilippo
2015-03-28  8:36   ` Richard Cochran
2015-03-28 13:55   ` Sergei Shtylyov
2015-03-28  8:28 ` Richard Cochran
2015-03-28 18:26   ` David Miller
2015-03-30 22:51   ` Sergei Shtylyov
2015-03-31  6:43     ` Richard Cochran
2015-03-31  9:01       ` Richard Cochran
2015-03-31 15:38       ` David Miller
2015-03-31 17:40         ` Sergei Shtylyov
2015-03-31 17:48           ` David Miller
2015-04-03  6:27             ` masaru.nagai.vx
2015-04-12 22:03               ` Sergei Shtylyov [this message]
2015-04-09 13:11       ` Bjørn Mork
2015-04-09 17:57         ` David Miller
2015-04-13 20:23     ` Sergei Shtylyov
2015-04-14  5:27       ` Richard Cochran
2015-04-14 10:14         ` Sergei Shtylyov
2015-04-14 16:30           ` Richard Cochran
2015-04-14 16:58             ` Sergei Shtylyov
2015-04-14 18:30               ` Richard Cochran
2015-04-15  1:01                 ` masaru.nagai.vx
2015-04-15  5:31                   ` Richard Cochran
2015-04-02 13:56 ` Ben Hutchings
2015-04-13 20:34   ` Sergei Shtylyov
2015-04-13 22:13     ` Lino Sanfilippo
2015-04-13 22:31       ` Ben Hutchings
2015-04-13 22:53         ` Lino Sanfilippo
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=552AEBA4.405@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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).