Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751777AbdFIXRq (ORCPT ); Fri, 9 Jun 2017 19:17:46 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:36022 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751687AbdFIXRo (ORCPT ); Fri, 9 Jun 2017 19:17:44 -0400 Date: Fri, 9 Jun 2017 16:17:41 -0700 From: Brian Norris To: Chris Packham Cc: boris.brezillon@free-electrons.com, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, andrew@lunn.ch, David Woodhouse , Marek Vasut , Richard Weinberger , Cyrille Pitchen Subject: Re: [PATCH v6] mtd: handle partitioning on devices with 0 erasesize Message-ID: <20170609231741.GP102137@google.com> References: <20170609035831.6258-1-chris.packham@alliedtelesis.co.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170609035831.6258-1-chris.packham@alliedtelesis.co.nz> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 556 Lines: 13 Thanks Chris! On Fri, Jun 09, 2017 at 03:58:31PM +1200, Chris Packham wrote: > erasesize is meaningful for flash devices but for SRAM there is no > concept of an erase block so erasesize is set to 0. When partitioning > these devices instead of ensuring partitions fall on erasesize > boundaries we ensure they fall on writesize boundaries. > > Helped-by: Boris Brezillon > Signed-off-by: Chris Packham Looks good to me. Did Boris have any last thoughts? Or else I'll merge this.