Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp193417imj; Thu, 7 Feb 2019 02:51:01 -0800 (PST) X-Google-Smtp-Source: AHgI3IaYItLX5kaqnZLweaDpkXgalFDuwc+xEdg3JD+tWPFotkW1hRajTO9Jb5wlBdklVMOCmN8z X-Received: by 2002:a63:e21:: with SMTP id d33mr346986pgl.272.1549536661508; Thu, 07 Feb 2019 02:51:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549536661; cv=none; d=google.com; s=arc-20160816; b=cAmn6B7QdcvngXO2zxRjbDwsMxeYY2nIbhy2GDrB7ojZ8BMk7/06l1aZEGId65CGu/ QrZMqbcFMMZtVmTMG10zxEPfLPdEilT6FLAaclO1f6w8JQZGuhCG9+rKHaJ/rXFiIO9A tSqMMjZ4NHiQx94y6XfZap/YMbMw//rkguH+5a6FTFe8P5i4TNd1IqZajD7ntfh8teV1 mABa+s95tpuDcN9dRoLQiYrRifU0h2i2ibBMJXnqeS/FG54lkCELpTka6Cjr7P/RyzPE aKuv7P0jbpKNQWCktRFaPWut4sTQUOzwNcvh+vqsazNcBP4DuP9x/u7MYZEncYthgWHU qdmw== 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 :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=XXhe4QMF89ZT/f0yt7nFT7CGMxUkdBi3LfkX5HNVjNY=; b=CcS53M0+68M6goGsuNB/NohuYo6/vTEA7fbdsUSA53DJ+FGkY3jermI98OvnCXWKLK aDfDKTSGoOr1iopEhEYUDHy+5xJEyU62ekOH2SdooTB+19G+aCorrWFNwLVgkmY8g6Zl WqJGWLv9OcS0EV/hLVfR5nLbRpNpDy81KxOGZaJPAI6nL/BzpMU0n7cJ/d2Wxb7usrZS b8NkY7BrcnMSUihDYSvrTtJbv4sIUGfo7DnQsAnw+VUy5WmuHUcBds+KqoDHR9CYvtrL U71dmY4dGIpT7AKOB6H9yMGPiBtpOMFCNaG/TUG1iedr1yFOIEcthlC09i5MRPa5B7i2 ImrA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cb2si1191074plb.201.2019.02.07.02.50.46; Thu, 07 Feb 2019 02:51:01 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726868AbfBGKs4 (ORCPT + 99 others); Thu, 7 Feb 2019 05:48:56 -0500 Received: from bhuna.collabora.co.uk ([46.235.227.227]:50038 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726186AbfBGKs4 (ORCPT ); Thu, 7 Feb 2019 05:48:56 -0500 Received: from localhost (unknown [IPv6:2a01:e0a:2c:6930:5cf4:84a1:2763:fe0d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: bbrezillon) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id CAB9927E636; Thu, 7 Feb 2019 10:48:54 +0000 (GMT) Date: Thu, 7 Feb 2019 11:48:50 +0100 From: Boris Brezillon To: Cc: , , , , , , Subject: Re: [PATCH 1/2] mtd: spi-nor: Add support for EN25Q80A Message-ID: <20190207114843.01c431dd@kernel.org> In-Reply-To: <5bdbd64f-bacd-8192-b7eb-6ec4c06baec0@microchip.com> References: <20190123075538.12681-1-frieder.schrempf@kontron.de> <52338dfe-aca1-503d-6871-c4be09f1f3ac@kontron.de> <5bdbd64f-bacd-8192-b7eb-6ec4c06baec0@microchip.com> Organization: Collabora X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 7 Feb 2019 10:16:05 +0000 wrote: > Hi, Frieder, > > On 02/07/2019 12:06 PM, Schrempf Frieder wrote: > > Hi Tudor, > > > > On 03.02.19 14:33, Tudor.Ambarus@microchip.com wrote: > >> Hi, Frieder, > >> > >> On 01/23/2019 09:56 AM, Schrempf Frieder wrote: > >>> From: Frieder Schrempf > >>> > >>> This adds support for the EON EN25Q80A, a 8Mb SPI NOR chip. > >> I would suggest to specify who is using this flash and how did you test it. This > >> way we will not end up with support for flashes that are not actually used. > > Ok. The flash is used by a board that I plan to upstream. Maybe I should > > just resubmit this together with the actual board support patches? No need to wait for the board patches, they'll be applied independently anyway. Just mention the board you tested it on in the commit message (even if it's not upstream yet) and we should be good. Thanks, Boris