From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753465AbbCaJZd (ORCPT ); Tue, 31 Mar 2015 05:25:33 -0400 Received: from verein.lst.de ([213.95.11.211]:54639 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752379AbbCaJZ2 (ORCPT ); Tue, 31 Mar 2015 05:25:28 -0400 Date: Tue, 31 Mar 2015 11:25:26 +0200 From: Christoph Hellwig To: Boaz Harrosh Cc: Christoph Hellwig , linux-nvdimm@ml01.01.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, ross.zwisler@linux.intel.com, axboe@kernel.dk Subject: Re: another pmem variant V2 Message-ID: <20150331092526.GA25958@lst.de> References: <1427358764-6126-1-git-send-email-hch@lst.de> <55143A8B.2060304@plexistor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55143A8B.2060304@plexistor.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 26, 2015 at 06:57:47PM +0200, Boaz Harrosh wrote: > On 03/26/2015 10:32 AM, Christoph Hellwig wrote: > > Here is another version of the same trivial pmem driver, because two > > obviously aren't enough. The first patch is the same pmem driver > > that Ross posted a short time ago, just modified to use platform_devices > > to find the persistant memory region instead of hardconding it in the > > Kconfig. This allows to keep pmem.c separate from any discovery mechanism, > > but still allow auto-discovery. > > > > Hi Christoph > > So I've been trying to test your version, and play around with it. > I currently have some problems, but this is the end of the week for me > so I will debug and fix it after the weekend on Sunday. Any news? I'd really like to resend this ASAP to get it into 4.1..