From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 01110B708C for ; Tue, 9 Jun 2009 02:35:53 +1000 (EST) Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [92.198.50.35]) by ozlabs.org (Postfix) with ESMTP id 854A8DDD0C for ; Tue, 9 Jun 2009 02:35:51 +1000 (EST) Date: Mon, 8 Jun 2009 18:35:40 +0200 From: Wolfram Sang To: Grant Likely Subject: Re: [PATCH V2 2/2] mtd/maps/mtd-ram: add an of-platform driver Message-ID: <20090608163540.GA16384@pengutronix.de> References: <1244203514-12516-1-git-send-email-w.sang@pengutronix.de> <1244203514-12516-3-git-send-email-w.sang@pengutronix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" In-Reply-To: Cc: devicetree-discuss@ozlabs.org, albrecht.dress@arcor.de, linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org, Ben Dooks , David Woodhouse List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > Question: why is bank-width even relevant for a RAM device? The underlying map_ram-driver uses it once while erasing. The question rema= ins if this is really needed? And: Does this need to get solved before merging = my patches because changing the binding afterwards is hard? Or can they go mainline nevertheless? Thanks, Wolfram --=20 Pengutronix e.K. | Wolfram Sang | Industrial Linux Solutions | http://www.pengutronix.de/ | --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkotPdwACgkQD27XaX1/VRtCFgCdG3OTwgCSa2f7XfeouY/s4UWO glkAn1KU3AwcC2lVVuy9oFvNdXpPU8wD =pEkx -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--