From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH/RFC net-next 3/5] ravb: do not write 1 to reserved bits Date: Tue, 17 Apr 2018 10:15:53 -0400 (EDT) Message-ID: <20180417.101553.1512039208518397234.davem@davemloft.net> References: <20180417085030.32650-1-horms+renesas@verge.net.au> <20180417085030.32650-4-horms+renesas@verge.net.au> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: sergei.shtylyov@cogentembedded.com, magnus.damm@gmail.com, netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org, wsa+renesas@sang-engineering.com, kazuya.mizuguchi.ks@renesas.com To: horms+renesas@verge.net.au Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:55818 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752273AbeDQOPy (ORCPT ); Tue, 17 Apr 2018 10:15:54 -0400 In-Reply-To: <20180417085030.32650-4-horms+renesas@verge.net.au> Sender: netdev-owner@vger.kernel.org List-ID: From: Simon Horman Date: Tue, 17 Apr 2018 10:50:28 +0200 > From: Kazuya Mizuguchi > > This patch corrects writing 1 to reserved bits. > The write value should be 0. > > Signed-off-by: Kazuya Mizuguchi > Signed-off-by: Simon Horman How are we ending up in situations where the driver is trying to write non-zero values to those fields in the first place? The places creating those values should be making sure that the reserved bits are never set. If you mask out the reserved bits in the register writing locations, this just hides bugs.