Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753821AbdFMRBh (ORCPT ); Tue, 13 Jun 2017 13:01:37 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:32816 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753769AbdFMRBf (ORCPT ); Tue, 13 Jun 2017 13:01:35 -0400 Date: Tue, 13 Jun 2017 10:01:31 -0700 From: Brian Norris To: Boris Brezillon Cc: Chris Packham , 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: <20170613170131.GQ102137@google.com> References: <20170609035831.6258-1-chris.packham@alliedtelesis.co.nz> <20170610080042.58479317@bbrezillon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170610080042.58479317@bbrezillon> 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: 677 Lines: 15 On Sat, Jun 10, 2017 at 08:00:42AM +0200, Boris Brezillon wrote: > On Fri, 9 Jun 2017 15:58:31 +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 > > Acked-by: Boris Brezillon Thanks. Applied to l2-mtd.git