From: "wanghai (M)" <wanghai38@huawei.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: <UNGLinuxDriver@microchip.com>, <vladimir.oltean@nxp.com>,
<claudiu.manoil@nxp.com>, <alexandre.belloni@bootlin.com>,
<andrew@lunn.ch>, <vivien.didelot@gmail.com>,
<f.fainelli@gmail.com>, <davem@davemloft.net>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] net: dsa: felix: Make some symbols static
Date: Sat, 18 Jul 2020 18:49:10 +0800 [thread overview]
Message-ID: <dea3b332-8af7-b8db-6182-702b91ceeae4@huawei.com> (raw)
In-Reply-To: <20200718104027.ugsdw42jfcpewfl6@skbuf>
Thanks for reminding me, I'll do it.
在 2020/7/18 18:40, Vladimir Oltean 写道:
> On Sat, Jul 18, 2020 at 06:01:58PM +0800, Wang Hai wrote:
>> Fix sparse build warning:
>>
>> drivers/net/dsa/ocelot/felix_vsc9959.c:560:19: warning:
>> symbol 'vsc9959_vcap_is2_keys' was not declared. Should it be static?
>> drivers/net/dsa/ocelot/felix_vsc9959.c:640:19: warning:
>> symbol 'vsc9959_vcap_is2_actions' was not declared. Should it be static?
>>
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Wang Hai <wanghai38@huawei.com>
>> ---
> Please update your tree.
>
> commit 3ab4ceb6e9639e4e42d473e46ae7976c24187876
> Author: Vladimir Oltean <vladimir.oltean@nxp.com>
> Date: Sat Jun 20 18:43:36 2020 +0300
>
> net: dsa: felix: make vcap is2 keys and actions static
>
> Get rid of some sparse warnings.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>> drivers/net/dsa/ocelot/felix_vsc9959.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/dsa/ocelot/felix_vsc9959.c b/drivers/net/dsa/ocelot/felix_vsc9959.c
>> index 1dd9e348152d..2067776773f7 100644
>> --- a/drivers/net/dsa/ocelot/felix_vsc9959.c
>> +++ b/drivers/net/dsa/ocelot/felix_vsc9959.c
>> @@ -557,7 +557,7 @@ static const struct ocelot_stat_layout vsc9959_stats_layout[] = {
>> { .offset = 0x111, .name = "drop_green_prio_7", },
>> };
>>
>> -struct vcap_field vsc9959_vcap_is2_keys[] = {
>> +static struct vcap_field vsc9959_vcap_is2_keys[] = {
>> /* Common: 41 bits */
>> [VCAP_IS2_TYPE] = { 0, 4},
>> [VCAP_IS2_HK_FIRST] = { 4, 1},
>> @@ -637,7 +637,7 @@ struct vcap_field vsc9959_vcap_is2_keys[] = {
>> [VCAP_IS2_HK_OAM_IS_Y1731] = {182, 1},
>> };
>>
>> -struct vcap_field vsc9959_vcap_is2_actions[] = {
>> +static struct vcap_field vsc9959_vcap_is2_actions[] = {
>> [VCAP_IS2_ACT_HIT_ME_ONCE] = { 0, 1},
>> [VCAP_IS2_ACT_CPU_COPY_ENA] = { 1, 1},
>> [VCAP_IS2_ACT_CPU_QU_NUM] = { 2, 3},
>> --
>> 2.17.1
>>
> Thanks,
> -Vladimir
>
> .
>
prev parent reply other threads:[~2020-07-18 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 10:01 Wang Hai
2020-07-18 10:40 ` Vladimir Oltean
2020-07-18 10:49 ` wanghai (M) [this message]
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=dea3b332-8af7-b8db-6182-702b91ceeae4@huawei.com \
--to=wanghai38@huawei.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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
all inboxes | Powered by JetHome®