Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752363AbZIVXBt (ORCPT ); Tue, 22 Sep 2009 19:01:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751826AbZIVXBs (ORCPT ); Tue, 22 Sep 2009 19:01:48 -0400 Received: from ru.mvista.com ([213.79.90.228]:51239 "EHLO buildserver.ru.mvista.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751678AbZIVXBr (ORCPT ); Tue, 22 Sep 2009 19:01:47 -0400 Date: Wed, 23 Sep 2009 03:01:50 +0400 From: Anton Vorontsov To: Andrew Morton Cc: David Brownell , ben@fluff.org, dwmw2@infradead.org, grant.likely@secretlab.ca, benh@kernel.crashing.org, khali@linux-fr.org, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org, linuxppc-dev@ozlabs.org Subject: Re: [PATCH 2/6] mtd: m25p80: Convert to device table matching Message-ID: <20090922230150.GA27593@oksana.dev.rtsoft.ru> Reply-To: avorontsov@ru.mvista.com References: <20090731003957.GA23982@oksana.dev.rtsoft.ru> <20090731004100.GB8371@oksana.dev.rtsoft.ru> <200908031954.50955.david-b@pacbell.net> <20090922141705.b5d31e24.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20090922141705.b5d31e24.akpm@linux-foundation.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1722 Lines: 46 On Tue, Sep 22, 2009 at 02:17:05PM -0700, Andrew Morton wrote: > On Mon, 3 Aug 2009 19:54:50 -0700 > David Brownell wrote: > > > On Thursday 30 July 2009, Anton Vorontsov wrote: > > > This patch converts the m25p80 driver so that now it uses .id_table > > > for device matching, making it properly detect devices on OpenFirmware > > > platforms (prior to this patch the driver misdetected non-JEDEC chips, > > > seeing all chips as "m25p80"). > > > > I suspect "detect" is a misnomer there. It only "detects" JEDEC chips. > > All others got explicit declarations ... so if there's misbehavior for > > other chips, it's because those declarations were poorly handled. Maybe > > they were not properly flagged as non-JDEC > > > > > > > Also, now jedec_probe() only does jedec probing, nothing else. If it > > > is not able to detect a chip, NULL is returned and the driver fall > > > backs to the information specified by the platform (platform_data, or > > > exact ID). > > > > I'd rather keep the warning, so there's a clue about what's really > > going on: JEDEC chip found, but its ID is not handled. > > > > afaik there was no response to David's review comments, so this patch > is in the "stuck" state. Hm? Response: http://lkml.org/lkml/2009/8/18/363 And the two patches I sent on top: http://lkml.org/lkml/2009/8/18/364 http://lkml.org/lkml/2009/8/18/366 -- Anton Vorontsov email: cbouatmailru@gmail.com irc://irc.freenode.net/bd2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/