Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751534AbdFHXka (ORCPT ); Thu, 8 Jun 2017 19:40:30 -0400 Received: from gate2.alliedtelesis.co.nz ([202.36.163.20]:56627 "EHLO gate2.alliedtelesis.co.nz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751428AbdFHXk3 (ORCPT ); Thu, 8 Jun 2017 19:40:29 -0400 From: Chris Packham To: Brian Norris CC: "linux-mtd@lists.infradead.org" , "andrew@lunn.ch" , "dwmw2@infradead.org" , "boris.brezillon@free-electrons.com" , "linux-kernel@vger.kernel.org" , Marek Vasut , "Richard Weinberger" , Cyrille Pitchen Subject: Re: [PATCH v5 4/5] mtd: mchp23k256: add partitioning support Thread-Topic: [PATCH v5 4/5] mtd: mchp23k256: add partitioning support Thread-Index: AQHS209REmLtsBhhjUKbT3e6Tb65CQ== Date: Thu, 8 Jun 2017 23:40:20 +0000 Message-ID: References: <20170602032119.22282-1-chris.packham@alliedtelesis.co.nz> <20170602032119.22282-5-chris.packham@alliedtelesis.co.nz> <20170608233346.GI102137@google.com> Accept-Language: en-NZ, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [2001:df5:b000:22:c463:af31:f446:c778] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v58Neb0x014949 Content-Length: 672 Lines: 19 On 09/06/17 11:33, Brian Norris wrote: > On Fri, Jun 02, 2017 at 03:21:18PM +1200, Chris Packham wrote: >> Setting the of_node for the mtd device allows the generic mtd code to >> setup the partitions. >> >> Signed-off-by: Chris Packham >> Reviewed-by: Andrew Lunn >> Tested-by: Andrew Lunn > > Applied patches 4 and 5, with an editorial note on this one, to note the > outstanding issue about fixing up the eraseblock-boundary check in the > partitioning code. > > 1 and 2 were already applied, and I had a change request on patch 3. Thanks Brian, I'll take a look at the suggestions on patch 3.