Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1391572ybe; Fri, 6 Sep 2019 17:16:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqxExoQeWsSpg8DeNl4e1LIzRsLDm7/ipAy+gKiYrYmZVebrVKyw7GU7CE9y7ZXB9pyRh/E9 X-Received: by 2002:a63:595d:: with SMTP id j29mr10451368pgm.134.1567815387952; Fri, 06 Sep 2019 17:16:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567815387; cv=none; d=google.com; s=arc-20160816; b=ZUNqHYfhyB1W8d7rTRFrPV23YRmJkbT11YVkMedkyqDBQ3SkUKiWPzrztMYKVZPTmX 3a5od0UnYXPNs5N7rMn2461JZvhTLEWmHJjIzB2SpVp7VkrynoUzohC0xHtvpHeFhtyx RZ5LPvXot7xiZwLoarxWWTlIEUwJrvAzIpDmYvwRmyeq9IuvUeU+FETtv+o2suFCG7RB Llq1F6RrvB8OUYSySp8bs7AqkOQaRqdgUZPVnHVAcVQ8mFa7L0h7ANN6F+FXnHHcQ94O 3O0l+N2lQwiEVQjlyy34s8gyaJvG49T7raTKwW4EDysvanp+6odBROfNNWQXnb6t+XkO oV0A== 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=vPWtVERLkkuBxYBGUG/YWFOjIHGV6U1eedZ3x/NXqno=; b=BUq6+h6ilVkV3QZGnlJ3dkn/JTUFN/tZ2UsSCiICu+1ZOj838BqySNmoCaF1xtjJZe kdIB0fbPIhmskOAXnHcVCa9LzpcFCFiV+UeT2MabBCmGromlDJBgHBbCvynBlIOHt1Ep V7RY3oTAnsMSns5G+5T9D4v79Z2BCw4Px3AdDH2Hlb4oyyAXyswJTDlSfTlCHs9RVTAU QGHfOMdE+N8VQB1Z35B7LKfizuH7zIBzM5vLDbt5tfPoxsH/fiFQ8uDjxIaJx4/286ZA CBuZ2H8yKNYDlrUHQ9pJkg+tLhRdXPUmdFVnhqD454+M3bHE/BsPv7HBnRnNIyftxvZL ojeg== 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 h91si6138899pld.3.2019.09.06.17.16.12; Fri, 06 Sep 2019 17:16:27 -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 S2392374AbfIFO6x (ORCPT + 99 others); Fri, 6 Sep 2019 10:58:53 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:50112 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726019AbfIFO6x (ORCPT ); Fri, 6 Sep 2019 10:58:53 -0400 Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id DF006601A9709E8FC318; Fri, 6 Sep 2019 22:58:49 +0800 (CST) Received: from [127.0.0.1] (10.202.227.238) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.439.0; Fri, 6 Sep 2019 22:58:45 +0800 Subject: Re: [PATCH] docs: mtd: Update spi nor reference driver To: Jonathan Corbet References: <1565107583-68506-1-git-send-email-john.garry@huawei.com> <20190906085212.79ec917c@lwn.net> CC: , , , , From: John Garry Message-ID: <9110efc4-35e6-ff04-1a6d-d5d9f93927de@huawei.com> Date: Fri, 6 Sep 2019 15:58:41 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20190906085212.79ec917c@lwn.net> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.227.238] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/09/2019 15:52, Jonathan Corbet wrote: > On Wed, 7 Aug 2019 00:06:23 +0800 > John Garry wrote: > >> The reference driver no longer exists since commit 50f1242c6742 ("mtd: >> fsl-quadspi: Remove the driver as it was replaced by spi-fsl-qspi.c"). >> >> Update reference to spi-fsl-qspi.c driver. >> >> Signed-off-by: John Garry > > So this appears to have languished for a month...applied now, sorry for > the delay. > > Thanks, > > jon > > . > Hi Jon, I don't think that it was appropriate to apply this patch in the end - maybe this could have been communicated better. If you check the subsequent discussion in this thread, it seems that completely new documentation is required: "Actually it seems like the whole file is obsolete and needs to be removed or replaced by proper documentation of the SPI MEM API." But nothing seems to be happening there... Thanks, John