From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: [PATCH v7 03/22] axonram: Fix bug in direct_access Date: Wed, 2 Apr 2014 15:24:46 -0400 Message-ID: <20140402192446.GC27299@linux.intel.com> References: <20140329162216.GC1211@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Matthew Wilcox , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org To: Jan Kara Return-path: Content-Disposition: inline In-Reply-To: <20140329162216.GC1211@quack.suse.cz> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Mar 29, 2014 at 05:22:16PM +0100, Jan Kara wrote: > On Sun 23-03-14 15:08:29, Matthew Wilcox wrote: > > The 'pfn' returned by axonram was completely bogus, and has been since > > 2008. > Maybe time to drop the driver instead? When noone noticed for 6 years, it > seems pretty much dead... Or is there some possibility the driver can get > reused for new HW? It may be in use, just not with the -o xip option to ext2 ... I can't find out which of the various vendors on the internet that are called 'Axon' that this device was originally supposed to support. I suspect it's dead, since it's DDR-2, but *shrug*, it costs little to fix it.