Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4868600yba; Wed, 10 Apr 2019 06:39:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqwJzIX9KJ8VAJKTGT4OIR81unTeh6mOCQioG9+iRW8b4/Rsxe8Tte+ruqhsXfXWpnYYI7Yj X-Received: by 2002:a63:d1f:: with SMTP id c31mr40394693pgl.353.1554903588646; Wed, 10 Apr 2019 06:39:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554903588; cv=none; d=google.com; s=arc-20160816; b=NHaQWYCOKWXmhuLBcbCFonYEp9XMUp+w0c2ZNHJvnsMvc7YVlAVc2I+0lhibQXS2Q/ DUzfS18LZ3MnFjOTPHe0G/xXv+xfqP2amp9bHTeaQiTMaiJdYr8006qpzLDTIgRmkWt2 KdzZBoK/SRcbZw/4GRi4ZhGd8bKfjf/09hrKh+7Q/NN6UcnHw0in1geJiyGf2zt6TLvx vlO7T6QtWcIZohFpBU0yCQsMr11c49gfmb5PWw18Q2fhfTG4ZKtuW5N0iwgOVG5wFV+R GhHCkEZWi82EJVT5mQI5aTFEe7iDAL0JXDzjjBCmHh+J4GKcZxrnhAqptIFqfMEFcfGi bWmw== 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:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=FWz29aM2/UIu3thQXFoJxp+ZDGMhkp3vmjGGyYecVaE=; b=hOuqjC8uN+Wf7jPOh4Fq8pVuymeP2zCsGXzlD6rKbL4gefvzO4tY2pZzTDhuKtDRtC vziUvvHAnHZyA3qNJrUW3tH0X4cLnjHY0IbIGYMeB/yZEkUhpeUvuooynm+u8ci5q6Zl mA1VO7Luudfm19ArHdVN3G8+3i5UEOh/XHKwZZMGMO8rFu5sFmEVDswHiZ8yp34atbSM WiDQZUfcenKrB+/GY29FLiq1V/pTpM4g0nLEIO4/joYFZa5v+n1TFVZt9uLgg3ajgiof GkH0/hbrm76zC66yMo87TheKDPT+yWY3v27mrm0+9IMNvJaMLhsOjP8FdnSMsgqEgIhy XmNw== 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 61si5761906plf.290.2019.04.10.06.39.32; Wed, 10 Apr 2019 06:39:48 -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 S1732305AbfDJNKv (ORCPT + 99 others); Wed, 10 Apr 2019 09:10:51 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:6719 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729441AbfDJNKu (ORCPT ); Wed, 10 Apr 2019 09:10:50 -0400 Received: from DGGEMS407-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id A15CDCF8180C2EA6CFF3; Wed, 10 Apr 2019 21:10:45 +0800 (CST) Received: from [127.0.0.1] (10.177.31.96) by DGGEMS407-HUB.china.huawei.com (10.3.19.207) with Microsoft SMTP Server id 14.3.408.0; Wed, 10 Apr 2019 21:10:42 +0800 Subject: Re: [LINUX PATCH v3] spi: spi-mem: Fix build error without CONFIG_SPI_MEM To: Mark Brown , Naga Sureshkumar Relli References: <1554897429-5959-1-git-send-email-naga.sureshkumar.relli@xilinx.com> <2d9cee19-a776-ad18-b8ac-6d0d1b096ad6@huawei.com> <20190410122457.GP6106@sirena.org.uk> <20190410123558.GQ6106@sirena.org.uk> CC: "vigneshr@ti.com" , "linux-kernel@vger.kernel.org" , "linux-spi@vger.kernel.org" , Michal Simek , "nagasuresh12@gmail.com" From: YueHaibing Message-ID: <8316c6e9-9000-bd1e-aa96-3db069e61824@huawei.com> Date: Wed, 10 Apr 2019 21:10:42 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20190410123558.GQ6106@sirena.org.uk> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.31.96] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/4/10 20:35, Mark Brown wrote: > On Wed, Apr 10, 2019 at 12:30:37PM +0000, Naga Sureshkumar Relli wrote: > >>> Yeah, I'm surprised that builds... > >> Sorry, I tested with CONFIG_SPI_MEM enabled. It's my bad. > > I also see that I'd queued an earlier version for application. I've > lost track of whatever issues there were with that, sorry - could one of > you please post an incremental patch for them? IIRC they were nice to > haves and the patch that was applied fixes the correctness issue. Ok, there just make the stub helper to static inline I can post a new patch based my initial patch. >