From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752850AbdEQLmL (ORCPT ); Wed, 17 May 2017 07:42:11 -0400 Received: from vps0.lunn.ch ([178.209.37.122]:33279 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752956AbdEQLl7 (ORCPT ); Wed, 17 May 2017 07:41:59 -0400 Date: Wed, 17 May 2017 13:41:28 +0200 From: Andrew Lunn To: Chris Packham Cc: dwmw2@infradead.org, computersforpeace@gmail.com, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/4] mtd: mchp23k256: device tree and mchp23lcv1024 Message-ID: <20170517114128.GA19968@lunn.ch> References: <20170517053908.26138-1-chris.packham@alliedtelesis.co.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170517053908.26138-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 On Wed, May 17, 2017 at 05:39:04PM +1200, Chris Packham wrote: > This series adds device tree support to the mchp23k256 driver and > support for the mchp23lcv1024 chip. I suspect there are more compatible > variants that we could now enumerate if desired. Hi Chris Cool. I only have a mchp23k256, so that is what i targeted. And it is used on an Intel board, via a USB-SPI dongle, so i didn't need platform data. I considered partition support, but decided against it, for my use case. I can just about get a usable minix filesystem in 256K. But anything smaller seems silly to have a real filesystem on it. Andrew