From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id DBB5221951C94 for ; Tue, 25 Apr 2017 15:57:53 -0700 (PDT) Received: by mail-oi0-x22d.google.com with SMTP id j201so189912516oih.2 for ; Tue, 25 Apr 2017 15:57:53 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20170425222250.GC15722@omniknight.lm.intel.com> References: <20170425211651.7640-1-toshi.kani@hpe.com> <20170425214422.GB15722@omniknight.lm.intel.com> <1493156958.26622.8.camel@hpe.com> <20170425222250.GC15722@omniknight.lm.intel.com> From: Dan Williams Date: Tue, 25 Apr 2017 15:57:52 -0700 Message-ID: Subject: Re: [PATCH] libnvdimm: fix phys_addr for nvdimm_clear_poison List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Vishal Verma Cc: "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" List-ID: On Tue, Apr 25, 2017 at 3:22 PM, Vishal Verma wrote: > On 04/25, Kani, Toshimitsu wrote: >> On Tue, 2017-04-25 at 15:44 -0600, Vishal Verma wrote: >> > On 04/25, Toshi Kani wrote: > [...] >> > >> > Should we be using nsio->res.start here or nsio->addr ? >> >> nsio->addr is a virtual address. We need to pass the physical address >> of this range. > > I see - makes sense. > You can add > Reviewed-by: Vishal Verma Thanks, applied. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1955363AbdDYW6K (ORCPT ); Tue, 25 Apr 2017 18:58:10 -0400 Received: from mail-oi0-f44.google.com ([209.85.218.44]:35690 "EHLO mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2994100AbdDYW5y (ORCPT ); Tue, 25 Apr 2017 18:57:54 -0400 MIME-Version: 1.0 In-Reply-To: <20170425222250.GC15722@omniknight.lm.intel.com> References: <20170425211651.7640-1-toshi.kani@hpe.com> <20170425214422.GB15722@omniknight.lm.intel.com> <1493156958.26622.8.camel@hpe.com> <20170425222250.GC15722@omniknight.lm.intel.com> From: Dan Williams Date: Tue, 25 Apr 2017 15:57:52 -0700 Message-ID: Subject: Re: [PATCH] libnvdimm: fix phys_addr for nvdimm_clear_poison To: Vishal Verma Cc: "Kani, Toshimitsu" , "linux-kernel@vger.kernel.org" , "Jiang, Dave" , "linux-nvdimm@lists.01.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 25, 2017 at 3:22 PM, Vishal Verma wrote: > On 04/25, Kani, Toshimitsu wrote: >> On Tue, 2017-04-25 at 15:44 -0600, Vishal Verma wrote: >> > On 04/25, Toshi Kani wrote: > [...] >> > >> > Should we be using nsio->res.start here or nsio->addr ? >> >> nsio->addr is a virtual address. We need to pass the physical address >> of this range. > > I see - makes sense. > You can add > Reviewed-by: Vishal Verma Thanks, applied.