[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170828.212252.121365416573053421.davem@davemloft.net>
Date: Mon, 28 Aug 2017 21:22:52 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: yanhaishuang@...s.chinamobile.com
Cc: sathya.perla@...adcom.com, ajit.khaparde@...adcom.com,
sriharsha.basavapatna@...adcom.com, somnath.kotur@...adcom.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] be2net: Fix some u16 fields appropriately
From: 严海双 <yanhaishuang@...s.chinamobile.com>
Date: Tue, 29 Aug 2017 09:04:57 +0800
> The GET_TX_COMPL_BITS comes from amap_get which also returns a 32-bit value:
It never returns a value with more than 16-bits of significance for
this specific call.
Please stop trying to be semantically clever when arguing about this
change.
It's not about types, it's about what range of values the struct
member can actually hold.
Powered by blists - more mailing lists