Received: by 10.223.176.46 with SMTP id f43csp3345843wra; Mon, 22 Jan 2018 12:31:20 -0800 (PST) X-Google-Smtp-Source: AH8x224bmhCoOZgFWsCCoRl9Gjtcg8GQ/jf0Dyc4Sd9CesFVM9BldcgN3WsOLY1zt/Y4a67cUaWP X-Received: by 10.36.26.74 with SMTP id 71mr120016iti.32.1516653079855; Mon, 22 Jan 2018 12:31:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516653079; cv=none; d=google.com; s=arc-20160816; b=C9YQusW0ZEKdFEj8zjFgIZ89JRrDgqzWfhrcOmPsgrEGulwyNxlrNa2z4wi2ZKRmhx Bl5tdBGAWjEyiWTdVuAPOvVfpwSN3sz4PaOdxm/MALrtCky52OftcHCPy24Qg9H4wtP6 dU5rNmrJeg+eZLGBU1xVUQoYz5+9OzzYpLDKclGYdjvYz5ckIsJsiDDLfId9QQ5UzO0Z CCCfcNmMPyFLEoNhjfjWVjaTm6cAj/ZKBbbUQ/oJGyTbGrP5p6tF6DSDLwOKuxDCVSxn kploTdAzijRc6UzpE7zAJFj1AU4rhptN4pW/Qla/Af0QT+O1A1UyDy7r3ZJE9SdJ1zjn gIBQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature:arc-authentication-results; bh=0DG7T2M8k1/V3fCZwMQxeeVjsd9GOVj4N70ozujxc9o=; b=XqgHlsHKK1YLtL8DIfKVDjfKF1zMOMr8Fv52dQf1Ub6wBV2cXmKSAjzqA19q/c8VPy gimNdqLaEOlXzQY3Q1GmqdjRv62Rh0ufL/DPi55brKfDfW46q381lfDh5GFfOTASZd8Z Vtmi7H2u13HAW6Htc+Pt63wTpHpBzylY5g14djW2KOErPN3lwvDyNrctixh0X+AF3bHI XT0D9pP1BeK3l4eXi7x8VootoQrPDIhn5VrRTqDs0S2dY3ZvoRvk7Tk7JuHgmuzGcNn9 qmgGTX2OMGptiDL9RPgpqzuLFE3twQ54MvatTrihQMAC3tsXu/9JKfv0IWZUGrR/dXo8 1UWQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=QkbM10Cs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g194si6549831itb.32.2018.01.22.12.31.07; Mon, 22 Jan 2018 12:31:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=QkbM10Cs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751500AbeAVU3q (ORCPT + 99 others); Mon, 22 Jan 2018 15:29:46 -0500 Received: from mail-wr0-f182.google.com ([209.85.128.182]:39633 "EHLO mail-wr0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751037AbeAVU3n (ORCPT ); Mon, 22 Jan 2018 15:29:43 -0500 Received: by mail-wr0-f182.google.com with SMTP id z48so10110303wrz.6; Mon, 22 Jan 2018 12:29:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=0DG7T2M8k1/V3fCZwMQxeeVjsd9GOVj4N70ozujxc9o=; b=QkbM10CsgImFpbHJrqcUfOJB7ZyaDH3JGj4xsIQJh+s1N3gFPzMlyNuVnP6b5O0KN8 43CY2q7r7PwrwGcxsK4cgY4eaJJIAk1LXfTs65ygWmSbokrdUCFuey47U6CkyWvZ8CqJ 5/7pnaNTrS9Ijk0yZlVN/uJOngh3kKoNuNYFtYiXML6gOqdQKVaiyBeL7xf6NCcrJvdn 5br47NMqFabF6xeMf/pu7B8fqhyp1aGFsIbwHa4AJp497QL+pU3tgz2JEU2ruVpHRlAj c/IlduOaIjjdctUsA9cQCs/2nXcssT0wkfYfWw8IlbG//a4Ef549mGHIGw6Q9FNyUxQV mKPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=0DG7T2M8k1/V3fCZwMQxeeVjsd9GOVj4N70ozujxc9o=; b=SuZI/EFRSDsoK/LQW7Ml/UeMHM99JFFZSaTL3UHyZlEiYmodQWjfhrA2DyMmxo8iwv v85NA6mfXxneap9nGQ1e3z71PqKor8FjEgVgcC6WYKX8r5FX0Q6/8BmWk22O4KVTqDcd 2UJ2xk7Khi3J6i3LFIH5p6KiGfit1aWedWstEzL+Y4VRrq98x0nz1Odzzw2BJrRs2t/r Tg/HfH2GNMS7LG6mTvsRcOPNc4q4uaxVzOe4qFPQa/FoVtRI1bkEPL11lLk+bRIL5CRY 3jDtQlyHe3wzubpiDKPCEmmx5rT/TG5UkgPF5bkLBTXdPWG/bkxmG/Zhj3llD3bieGCq 7EEg== X-Gm-Message-State: AKwxytdyvdQWfM+XJtIxHo1/3yrMuy0XM/oeHlxMD9tGmbfhOSPE5Bni CgKckvZ2XGLDoOWgjMte61M= X-Received: by 10.223.161.12 with SMTP id o12mr66495wro.243.1516652981929; Mon, 22 Jan 2018 12:29:41 -0800 (PST) Received: from debian64.daheim (p200300D5FBC257FC0000000000000830.dip0.t-ipconnect.de. [2003:d5:fbc2:57fc::830]) by smtp.gmail.com with ESMTPSA id 5sm13605607wre.35.2018.01.22.12.29.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 22 Jan 2018 12:29:40 -0800 (PST) Received: from localhost.daheim ([127.0.0.1] helo=debian64.localnet) by debian64.daheim with esmtp (Exim 4.90) (envelope-from ) id 1ediiq-0005lf-2W; Mon, 22 Jan 2018 21:29:40 +0100 From: Christian Lamparter To: Ivan Mikhaylov Cc: "David S . Miller" , Rob Herring , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] net/ibm/emac: wrong bit is used for STA control register write Date: Mon, 22 Jan 2018 21:29:39 +0100 Message-ID: <9040166.kDGxHD26M5@debian64> In-Reply-To: <20180122190146.22876-1-ivan@de.ibm.com> References: <2818110.k5nooOEKBD@debian64> <20180122190146.22876-1-ivan@de.ibm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, January 22, 2018 8:01:46 PM CET Ivan Mikhaylov wrote: > >Something looks wrong here?! The commit message talks about bit 18, 19 and 20. > >However, 0x0800, 0x1000, 0x2000 and are like bit 11, 12 and 13? Furthermore, > >what about the EMAC_STACR_STAC_MASK? shouldn't it be 0x1800 now (or delete it > >since it doesn't look like it's used anywhere?). > Christian, nope, it's all fine there, it's big endian. Ok Thanks. I think I found the relevant info on Wikipedia: "Little-endian CPUs usually employ "LSB 0" bit numbering, however both bit numbering conventions can be seen in big-endian machines. Some architectures like SPARC and Motorola 68000 use "LSB 0" bit numbering, while S/390, PowerPC and PA-RISC use "MSB 0"." But as far as the kernel (code) is concerned, all architectures (big or little endian) have the same BIT marco: |#define BIT(nr) (1UL << (nr)) So if someone tries to #define EMAC_STACR_STAC_WRITE BIT(18) it would be 0x40000 instead. This is where the confusion is coming from. Can you please at least mention this somewhere that all the bits in the commit message are in "MSB 0" format? It's confusing enough as it is ;). > This commit related only > to write operation, I'll check MASK and see what I can do with that. Well, the MASK is not used and it now looks odd. So you might as well delete it. Maybe as well as all the unused EMACX_STACR_STAC_IND_* macros? Thanks, Christian