From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237] helo=passion.cambridge.redhat.com) by pentafluge.infradead.org with esmtp (Exim 3.22 #1 (Red Hat Linux)) id 172aNw-0000aH-00 for ; Tue, 30 Apr 2002 17:21:48 +0100 From: David Woodhouse In-Reply-To: <01ff01c1f049$b2a19fa0$bdb270d5@homeip.net> References: <01ff01c1f049$b2a19fa0$bdb270d5@homeip.net> <012701c1f031$bc52eee0$bdb270d5@homeip.net> <00d201c1f02d$f672d580$bdb270d5@homeip.net> <30704.1020161437@redhat.com> <18096.1020169313@redhat.com> To: johan.adolfsson@axis.com Cc: linux-mtd@lists.infradead.org Subject: Re: [PATCH/RFC] Create mtdram device at runtime. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Apr 2002 17:21:24 +0100 Message-ID: <4685.1020183684@redhat.com> Sender: linux-mtd-admin@lists.infradead.org Errors-To: linux-mtd-admin@lists.infradead.org List-Help: List-Post: List-Subscribe: , List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: johan.adolfsson@axis.com said: > How about letting mtdram_init_device return an allocated mtd_info* > and the caller is responsible for cleaning it up? The hardcoded init > functions store the returned pointer in the static mtd_info variable > and do it's clean-up on exit. Seems reasonable. -- dwmw2