From: huangdaode <huangdaode@hisilicon.com>
To: Julia Lawall <julia.lawall@lip6.fr>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: hisilicon: constify hnae_buf_ops and hnae_ae_ops structures
Date: Wed, 20 Jan 2016 10:48:20 +0000 [thread overview]
Message-ID: <569F65F4.7060509@hisilicon.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1512070704360.2037@localhost6.localdomain6>
Hi Julia,
This patch is OK for me.
thanks
Ddaode Huang
On 2015/12/7 14:05, Julia Lawall wrote:
>
> On Sun, 6 Dec 2015, David Miller wrote:
>
>> From: Julia Lawall <Julia.Lawall@lip6.fr>
>> Date: Sun, 6 Dec 2015 17:24:57 +0100
>>
>>> The hnae_buf_ops and hnae_ae_ops structures are never modified, so declare
>>> them as const.
>>>
>>> Done with the help of Coccinelle.
>>>
>>> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>> This doesn't apply to net-next.
> OK, will check on it.
>
> julia
>
>>> I have the impression that this driver is not recorded properly in the
>>> MAINTAINERS file.
>> Patches welcome.
> Who is the mintainer? huangdaode?
>
> thanks,
> julia
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: huangdaode <huangdaode@hisilicon.com>
To: Julia Lawall <julia.lawall@lip6.fr>, David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: hisilicon: constify hnae_buf_ops and hnae_ae_ops structures
Date: Wed, 20 Jan 2016 18:48:20 +0800 [thread overview]
Message-ID: <569F65F4.7060509@hisilicon.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1512070704360.2037@localhost6.localdomain6>
Hi Julia,
This patch is OK for me.
thanks
Ddaode Huang
On 2015/12/7 14:05, Julia Lawall wrote:
>
> On Sun, 6 Dec 2015, David Miller wrote:
>
>> From: Julia Lawall <Julia.Lawall@lip6.fr>
>> Date: Sun, 6 Dec 2015 17:24:57 +0100
>>
>>> The hnae_buf_ops and hnae_ae_ops structures are never modified, so declare
>>> them as const.
>>>
>>> Done with the help of Coccinelle.
>>>
>>> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>> This doesn't apply to net-next.
> OK, will check on it.
>
> julia
>
>>> I have the impression that this driver is not recorded properly in the
>>> MAINTAINERS file.
>> Patches welcome.
> Who is the mintainer? huangdaode?
>
> thanks,
> julia
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
next prev parent reply other threads:[~2016-01-20 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 16:24 [PATCH] net: hisilicon: constify hnae_buf_ops and hnae_ae_ops structures Julia Lawall
2015-12-06 16:24 ` Julia Lawall
2015-12-07 3:51 ` David Miller
2015-12-07 3:51 ` David Miller
2015-12-07 6:05 ` Julia Lawall
2015-12-07 6:05 ` Julia Lawall
2016-01-20 10:48 ` huangdaode [this message]
2016-01-20 10:48 ` huangdaode
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=569F65F4.7060509@hisilicon.com \
--to=huangdaode@hisilicon.com \
--cc=davem@davemloft.net \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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 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.