Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6753404yba; Tue, 14 May 2019 13:03:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqzyD/wX+uCu84acfilhLpruTn+BlNw+bITA1PWJFmDbn0vh+r5alKP6M8tWUl81983BUzGe X-Received: by 2002:a63:7552:: with SMTP id f18mr37436737pgn.234.1557864202964; Tue, 14 May 2019 13:03:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557864202; cv=none; d=google.com; s=arc-20160816; b=BpkQj5g3OUNWhJANLJH4RLcGaRAe/oDSOP3BoTukAxJJ5hrdF+m683JP1tw2Ia7g33 KZntozMQhSw/g1T8mJRWlVh7WAsHUUjXKbghwhmnyQhlTakbab8rlRYwLx5HXw74214R m+HNAykpjWul+lcT20CUrVgXHm1EF7Re+hZPNDq7LL/MjyAW7zkSTSD6wf3+6hkhXyUm 9yN4VmlTIeNndkpx0NgCrjKK4GbcO/RiX/uzZekgeYOzzQPGsExeXnPeIGH5LNWaJz2i pRfzVnqi/ZF3dfC3vibDS1ttn8qhUzr0IckdpL299byKIEDHXQeD5IcZM6OzBKMgfLN1 rAAQ== 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=bRieCCAdDnH4F1/Su38cwwdH7x7+0b+ZG/8pc4UCuhI=; b=GWZYNKBibFi+AXMm2e3qZ3AukUqu5N0wxy4WOyQaRo9zgQmCBjrpJOPgIQomR6h45V oGLFtac8s5AKHoigkqDMuMSd37CQ+YTlKouwA9MMDQhsKoChzkLzNqAFYus5kphRLsL3 NM8KxFJf/RNEFdBc2zn6umjDScBssGURpF+TwY/n3lPsAOBP6CDPsQcZ2/XRqGtiXET9 6fVWnsUKJb8pUpT3zAkU7dO37aWaN3ZhnAPmTzrvJxov3iNTHAMU9U7lGCwjEO9hC1+W pyV27HvZ6odwx2l5hZpOMt5qnJ+zzRfMOC5tY0Z3SmScN0qc6eTNcavTadiaAAbV4ScC Habw== 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 r15si9560037pgi.16.2019.05.14.13.03.07; Tue, 14 May 2019 13:03:22 -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 S1726283AbfENUBm convert rfc822-to-8bit (ORCPT + 99 others); Tue, 14 May 2019 16:01:42 -0400 Received: from relay2-d.mail.gandi.net ([217.70.183.194]:42899 "EHLO relay2-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726044AbfENUBl (ORCPT ); Tue, 14 May 2019 16:01:41 -0400 X-Originating-IP: 46.193.9.130 Received: from xps13 (cust-west-pareq2-46-193-9-130.wb.wifirst.net [46.193.9.130]) (Authenticated sender: miquel.raynal@bootlin.com) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 8B2F240005; Tue, 14 May 2019 20:01:38 +0000 (UTC) Date: Tue, 14 May 2019 22:01:36 +0200 From: Miquel Raynal To: Schrempf Frieder Cc: Jeff Kletsky , Boris Brezillon , Richard Weinberger , David Woodhouse , Brian Norris , Marek Vasut , "linux-mtd@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] mtd: spinand: Add support for GigaDevice GD5F1GQ4UFxxG Message-ID: <20190514220136.5f4624ee@xps13> In-Reply-To: References: <20190510121727.29834-1-lede@allycomm.com> <3cb32209-f246-e562-2aee-fdf566a60b30@kontron.de> <1023ba21-b188-1dcc-3ecc-c563d4cb8a67@allycomm.com> Organization: Bootlin X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Schrempf, Schrempf Frieder wrote on Tue, 14 May 2019 16:11:28 +0000: > Hi Jeff, > > On 14.05.19 17:42, Jeff Kletsky wrote: > > On 5/13/19 6:56 AM, Schrempf Frieder wrote: > > > >> Hi Jeff, > >> > >> I just noticed I hit the wrong button and my previous reply was only > >> sent to the MTD list, so I'm resending with fixed recipients... > >> > >> On 10.05.19 14:17,lede@allycomm.com wrote: > >>> From: Jeff Kletsky > >>> > >>> The GigaDevice GD5F1GQ4UFxxG SPI NAND is in current production devices > >>> and, while it has the same logical layout as the E-series devices, > >>> it differs in the SPI interfacing in significant ways. > >>> > >>> To accommodate these changes, this patch also: > >>> > >>> * Adds support for two-byte manufacturer IDs > >>> * Adds #define-s for three-byte addressing for read ops > >>> > >>> http://www.gigadevice.com/datasheet/gd5f1gq4xfxxg/ > >>> > >>> Signed-off-by: Jeff Kletsky > >> Maybe it would be better to split this patch into three parts: > >> * Add support for two-byte device IDs > >> * Add #define-s for three-byte addressing for read ops > >> * Add support for GD5F1GQ4UFxxG > >> > >> Anyway the content looks good to me, so: > >> > >> Reviewed-by: Frieder Schrempf > >> > >> [...] > > > > Thanks for the time in review and good words! > > You're welcome! > > > My apologies for an incomplete git-send-email config that left > > me nameless in the headers. > > No problem, I guessed your name from the Signed-off-by tag ;) > > > I wasn't sure if that was direction to submit as three patches > > at this time, but would be happy to do so if the consensus is > > that it the direction to follow. > > I think it's common to separate logical different changes. This makes it > easier to read. > Also the preparation changes only touch the SPI NAND core. I guess > that's another reason why they should be separated from the > chip-specific changes. > > > At least for me, I feel that the other two don't really stand > > on their own without the context for their need. > > I don't think that's a problem. Just add a note to the commit message > that these core changes are needed to prepare for the GD5F1GQ4UFxxG support. > > Thanks, > Frieder I agree with Frieder, if you don't mind, please split this commit in three. Thanks, Miquèl