Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754613Ab0DSO7q (ORCPT ); Mon, 19 Apr 2010 10:59:46 -0400 Received: from kroah.org ([198.145.64.141]:54655 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753845Ab0DSO7p (ORCPT ); Mon, 19 Apr 2010 10:59:45 -0400 Date: Mon, 19 Apr 2010 07:59:34 -0700 From: Greg KH To: Tomas Winkler Cc: Johannes Berg , Kay Sievers , David Woodhouse , "Rafael J. Wysocki" , Emmanuel Grumbach , linux-kernel@vger.kernel.org Subject: Re: request_firmware API exhaust memory Message-ID: <20100419145934.GA10893@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 604 Lines: 16 On Mon, Apr 19, 2010 at 03:20:34PM +0300, Tomas Winkler wrote: > Lately we've been developing a device that rather more extensively > used request_firmware API in load and also using pm_notifiers to load > firmware. Do you have a pointer to your driver source anywhere that shows how you are trying to use the firmware api in this manner? thanks, greg k-h -- 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/