Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp428907ybi; Fri, 21 Jun 2019 02:03:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqxHDiPkemKTWiftc3gpl+DTmTgPjpq1L7E4QQ2L3Hh5Tx/35wLvYt9+VXeBrfXfojRGHi0A X-Received: by 2002:a63:5a02:: with SMTP id o2mr16668343pgb.93.1561107785092; Fri, 21 Jun 2019 02:03:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561107785; cv=none; d=google.com; s=arc-20160816; b=vYFzj/O8vmJxryNSq5S3TOl4wjNnFhar+uHHH1bz/ESNFViXXl97QBIKq442/oyiUY cOMavwUGUi4zl7nvQbXcWTuDGXkQNx+UbsvukvqjonQGv9sDhrrPvSMVXoqXl74k6JKz gkc8bmXPnpg/vCY1X0zikErEBgCgMAi4OdWi/oC1nanAM+HGI3b2HR3doN9xkSu42wKs C3BtPL27lyWxU0n+zsv+Z/5p4YRZQI9hTCqXJRMr8ytPez9oEDQRXwWBsSY397IfKnrn 2DA33rJ2Lh3tV9T1Ir24+6hZHY9LQsbEUcPzPMWE5YVn+4nvZ/ekXq4aJuPRCO8LhqlN AqpQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=4HzRDcacmGtqmGfE244Fy6uOAK8PIsDaZn0yNCgG68w=; b=yeTlXwu0bne8GHGRwazBaIRjcqB5F2cF7sc6mOtYHf3HCpYapMt/MbuSQOt2+w3qa5 S2RG9wfP6pueh/QT0mBH8Xls/LaQHSukS9a0wLOM1yXWs91dzHejvSzaOkmHcoFiEBhi R9Du2fsEmQDWDbv2thDPvrIPts1woKobtzev/+KoyW8IWbBi9aJO04hOz7kB0k+0Vh5U tPZAsw6Y6b7222seO2UcjGMOCfF7eoPVMkOlovF60qlfJQ+d7NyH6tjVVoTl022/9mO1 4a6gwKP21eR9+lZadNAjdc7xKmo3jWs7DEH13BPLHmh1gLlxrz03y0ird4xKNe71XIIw er4A== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e1si2197720pjr.28.2019.06.21.02.02.48; Fri, 21 Jun 2019 02:03:05 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726321AbfFUJBX (ORCPT + 99 others); Fri, 21 Jun 2019 05:01:23 -0400 Received: from mail-qt1-f195.google.com ([209.85.160.195]:40784 "EHLO mail-qt1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726210AbfFUJBW (ORCPT ); Fri, 21 Jun 2019 05:01:22 -0400 Received: by mail-qt1-f195.google.com with SMTP id a15so6150365qtn.7; Fri, 21 Jun 2019 02:01:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4HzRDcacmGtqmGfE244Fy6uOAK8PIsDaZn0yNCgG68w=; b=WC4ldDEqh98+jAK2BHEm6qqEMG9dtnaGvDu3ntwspsgB00CmgLUBlCt7EDfZd2KOMy ap8r+bTKn2gTmbE5DVHCYrIIZCAkxSvZz8wcj28ckx/Xj35J0u8KcqSmAPnCMnjX+EH4 6eDgOJZJ58IpRi8JKwcXX81iA1ZvLQKPmoqZBYo697zFqkHZmSOvi2yISRyz0f5iZDfT ts1wzluzC77gTqvHrNNY80yLsaW+11DwID26tNFBOEcrFOFe1Rbu4udL/dxmgoCrAG56 1Uhv96QUXp15dlQG+7w78hS3LnSucMLMVznZSFKExvKF8mVxsO4G3XOIq/btiADuX6+Q DfIg== X-Gm-Message-State: APjAAAUj8xhDtmMArrAMdIJKN82uVEBzoyfuVhhy3qo0RYPVDG0VWgM3 YdWty6fteiMjYnl3s/S/QtJvvsRZdLqCi6VAIb8= X-Received: by 2002:aed:33a4:: with SMTP id v33mr81342975qtd.18.1561107681874; Fri, 21 Jun 2019 02:01:21 -0700 (PDT) MIME-Version: 1.0 References: <20190617131918.2518727-1-arnd@arndb.de> In-Reply-To: From: Arnd Bergmann Date: Fri, 21 Jun 2019 11:01:01 +0200 Message-ID: Subject: Re: [PATCH] dmaengine: dw-edma: fix __iomem type confusion To: Gustavo Pimentel Cc: Vinod Koul , Dan Williams , Andy Shevchenko , Russell King , Joao Pinto , "dmaengine@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 21, 2019 at 10:53 AM Gustavo Pimentel wrote: > > > > static struct dentry *base_dir; > > static struct dw_edma *dw; > > -static struct dw_edma_v0_regs *regs; > > +static struct dw_edma_v0_regs __iomem *regs; > > Shouldn't the __iomem be next to dw_edma_v0_regs instead of the variable > name? I saw other drivers putting the __iomem next to the variable type, > therefore I assume it's the typical coding style. Yes, that seems more common indeed. Do you want to fix up both patches yourself when you apply them or should I send a new version? Arnd