From: Murali Karicheri <m-karicheri2@ti.com>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
<davem@davemloft.net>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [net-next PATCH] net: hsr: fix incorrect type usage for protocol variable
Date: Wed, 6 May 2020 16:49:59 -0400 [thread overview]
Message-ID: <5c820a16-9c5f-1536-c4ea-6cd7658178c1@ti.com> (raw)
In-Reply-To: <87368dufx9.fsf@intel.com>
Hi Vinicius,
On 5/6/20 1:33 PM, Vinicius Costa Gomes wrote:
> Hi Murali,
>
> Murali Karicheri <m-karicheri2@ti.com> writes:
>
>> Fix following sparse checker warning:-
>>
>> net/hsr/hsr_slave.c:38:18: warning: incorrect type in assignment (different base types)
>> net/hsr/hsr_slave.c:38:18: expected unsigned short [unsigned] [usertype] protocol
>> net/hsr/hsr_slave.c:38:18: got restricted __be16 [usertype] h_proto
>> net/hsr/hsr_slave.c:39:25: warning: restricted __be16 degrades to integer
>> net/hsr/hsr_slave.c:39:57: warning: restricted __be16 degrades to integer
>>
>> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>> ---
>
> I think this patch should go via the net tree, as it is a warning fix.
> Anyway...
>
> Acked-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
>
>
Thanks. I will re-send it with net prefix and you ack. I thought since
this is just a warning, it is not that serious to include in net tree.
--
Murali Karicheri
Texas Instruments
next prev parent reply other threads:[~2020-05-06 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 15:41 [net-next PATCH] net: hsr: fix incorrect type usage for protocol variable Murali Karicheri
2020-05-06 17:33 ` Vinicius Costa Gomes
2020-05-06 20:49 ` Murali Karicheri [this message]
2020-05-06 22:00 ` David Miller
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=5c820a16-9c5f-1536-c4ea-6cd7658178c1@ti.com \
--to=m-karicheri2@ti.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vinicius.gomes@intel.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).