From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Yoshihiro Kaneko <ykaneko0929@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH/RFC v4 net-next] ravb: Add dma queue interrupt support
Date: Sun, 7 Feb 2016 20:18:00 +0300 [thread overview]
Message-ID: <56B77C48.3010900@cogentembedded.com> (raw)
In-Reply-To: <CAH1o70+WbQ8qRtO9nez1aooCLVTX30Z1G4MBJPmTCKCpMNzqxw@mail.gmail.com>
On 02/07/2016 07:56 PM, Yoshihiro Kaneko 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>
>>
>>
>> [...]
>>
>>> diff --git a/drivers/net/ethernet/renesas/ravb_main.c
>>> b/drivers/net/ethernet/renesas/ravb_main.c
>>> index ac43ed9..076f25f 100644
>>> --- a/drivers/net/ethernet/renesas/ravb_main.c
>>> +++ b/drivers/net/ethernet/renesas/ravb_main.c
>>
>> [...]
>>>
>>> @@ -1215,29 +1332,64 @@ static const struct ethtool_ops ravb_ethtool_ops =
>>> {
>>> .get_ts_info = ravb_get_ts_info,
>>> };
>>>
>>> +static inline int hook_irq(unsigned int irq, irq_handler_t handler,
>>> + struct net_device *ndev, struct device *dev,
>>> + const char *ch)
>>> +{
>>> + char *name;
>>> + int error;
>>> +
>>> + name = devm_kasprintf(dev, GFP_KERNEL, "%s:%s", ndev->name, ch);
>>
>>
>> BTW, shouldn't we test 'name' for NULL here?
>
> Thanks.
> I will fix it to return -ENOMEM if 'name' is NULL.
Be sure to use '!name' -- it's preferred in the networking code.
> Thanks,
> kaneko
MBR, Sergei
next prev parent reply other threads:[~2016-02-07 17:18 UTC|newest]
Thread overview: 18+ 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-26 0:23 ` Simon Horman
2016-01-26 19:00 ` Sergei Shtylyov
2016-01-27 1:49 ` Simon Horman
2016-01-28 15:50 ` Sergei Shtylyov
2016-01-28 18:36 ` Sergei Shtylyov
2016-01-28 16:48 ` Sergei Shtylyov
2016-02-07 16:50 ` Yoshihiro Kaneko
2016-02-07 17:09 ` Sergei Shtylyov
2016-02-08 17:19 ` Yoshihiro Kaneko
2016-02-21 15:42 ` Sergei Shtylyov
2016-02-21 19:16 ` Sergei Shtylyov
2016-02-25 22:22 ` Sergei Shtylyov
2016-01-28 17:32 ` Sergei Shtylyov
2016-02-07 16:56 ` Yoshihiro Kaneko
2016-02-07 17:18 ` Sergei Shtylyov [this message]
2016-01-28 17:51 ` Sergei Shtylyov
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=56B77C48.3010900@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 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).