All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>,
	Yoshihiro Kaneko <ykaneko0929@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC v4 net-next] ravb: Add dma queue interrupt support
Date: Tue, 26 Jan 2016 19:00:34 +0000	[thread overview]
Message-ID: <56A7C252.3040707@cogentembedded.com> (raw)
In-Reply-To: <20160126002300.GA27856@verge.net.au>

Hello.

    Yoshihiro-san, there was no need to hurry -- net-next is still closed and 
by posting this patch to netdev you're only making DaveM upset...

On 01/26/2016 03:23 AM, Simon Horman wrote:

 >> From: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
>>
>> This patch supports the following interrupts.
>>
>> - One interrupt for multiple (descriptor, error, management)
>> - One interrupt for emac
>> - Four interrupts for dma queue (best effort rx/tx, network control rx/tx)
>>
>> This patch improve efficiency of the interrupt handler by adding the
>> interrupt handler corresponding to each interrupt source described
>> above. Additionally, it reduces the number of times of the access to
>> EthernetAVB IF.
>>
>> Signed-off-by: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
>> Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
>
> I have tested this patch and the result seems positive.

    Tested on gen3 only I guess?

> Please let me know if any more/different testing would help.

    Sanity testing on some gen2 SoC wouldn't hurt (if you have time).

[...]

> Please feel free to add:
>
> Tested-by: Simon Horman <horms+renesas@verge.net.au>

    Thank you!

MBR, Sergei


WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>,
	Yoshihiro Kaneko <ykaneko0929@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC v4 net-next] ravb: Add dma queue interrupt support
Date: Tue, 26 Jan 2016 22:00:34 +0300	[thread overview]
Message-ID: <56A7C252.3040707@cogentembedded.com> (raw)
In-Reply-To: <20160126002300.GA27856@verge.net.au>

Hello.

    Yoshihiro-san, there was no need to hurry -- net-next is still closed and 
by posting this patch to netdev you're only making DaveM upset...

On 01/26/2016 03:23 AM, Simon Horman wrote:

 >> From: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
>>
>> This patch supports the following interrupts.
>>
>> - One interrupt for multiple (descriptor, error, management)
>> - One interrupt for emac
>> - Four interrupts for dma queue (best effort rx/tx, network control rx/tx)
>>
>> This patch improve efficiency of the interrupt handler by adding the
>> interrupt handler corresponding to each interrupt source described
>> above. Additionally, it reduces the number of times of the access to
>> EthernetAVB IF.
>>
>> Signed-off-by: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
>> Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
>
> I have tested this patch and the result seems positive.

    Tested on gen3 only I guess?

> Please let me know if any more/different testing would help.

    Sanity testing on some gen2 SoC wouldn't hurt (if you have time).

[...]

> Please feel free to add:
>
> Tested-by: Simon Horman <horms+renesas@verge.net.au>

    Thank you!

MBR, Sergei


  reply	other threads:[~2016-01-26 19:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 15:52 [PATCH/RFC v4 net-next] ravb: Add dma queue interrupt support Yoshihiro Kaneko
2016-01-24 15:52 ` Yoshihiro Kaneko
2016-01-26  0:23 ` Simon Horman
2016-01-26  0:23   ` Simon Horman
2016-01-26 19:00   ` Sergei Shtylyov [this message]
2016-01-26 19:00     ` Sergei Shtylyov
2016-01-27  1:49     ` Simon Horman
2016-01-27  1:49       ` Simon Horman
2016-01-28 15:50       ` Sergei Shtylyov
2016-01-28 15:50         ` Sergei Shtylyov
2016-01-28 18:36         ` Sergei Shtylyov
2016-01-28 18:36           ` Sergei Shtylyov
2016-01-28 16:48 ` Sergei Shtylyov
2016-01-28 16:48   ` Sergei Shtylyov
2016-02-07 16:50   ` Yoshihiro Kaneko
2016-02-07 16:50     ` Yoshihiro Kaneko
2016-02-07 17:09     ` Sergei Shtylyov
2016-02-07 17:09       ` Sergei Shtylyov
2016-02-08 17:19       ` Yoshihiro Kaneko
2016-02-08 17:19         ` Yoshihiro Kaneko
2016-02-21 15:42         ` Sergei Shtylyov
2016-02-21 15:42           ` Sergei Shtylyov
2016-02-21 19:16           ` Sergei Shtylyov
2016-02-21 19:16             ` Sergei Shtylyov
2016-02-25 22:22             ` Sergei Shtylyov
2016-02-25 22:22               ` Sergei Shtylyov
2016-01-28 17:32 ` Sergei Shtylyov
2016-01-28 17:32   ` Sergei Shtylyov
2016-02-07 16:56   ` Yoshihiro Kaneko
2016-02-07 16:56     ` Yoshihiro Kaneko
2016-02-07 17:18     ` Sergei Shtylyov
2016-02-07 17:18       ` Sergei Shtylyov
2016-01-28 17:51 ` Sergei Shtylyov
2016-01-28 17:51   ` Sergei Shtylyov
2016-02-07 17:18   ` Yoshihiro Kaneko
2016-02-07 17:18     ` Yoshihiro Kaneko

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=56A7C252.3040707@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=davem@davemloft.net \
    --cc=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ykaneko0929@gmail.com \
    /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 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.