From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4DA581EFF90; Fri, 4 Apr 2025 13:34:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743773656; cv=none; b=WeBmdTiWPfHwcl3n3qchurBWWWtEgzpNKbQP1zZQuakkW4EpVohl4plMlGkp/jr3HMsavUwoWYqILqOtsYteRRx/CgNsgluJt0uXMWdKaEXXklyJhz/kVDGkwQ7H8lBQnmuiPS+PbZAq5GhZypQccBVjd9lwg9vxAuwuYioZUVk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743773656; c=relaxed/simple; bh=B6AmqiWAWAQHPpfTvZpYHk8KMpkuBOP+r7HbmOUmCgI=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=gp9CDmU8TsKyLDuoXwmd495LMRRKzju+drSENKQySPbqusrYuD945eMlpMXpTGD2TZSK5rSkQvmelmwLehorK1wUeJm94vQEHKbWA0uMEZZnHlCoYb3Y55MxwJxMJnS28LOM/mS3l5KZ/8DJi2Q/xSBnlu1zvy9kQqA4t2ykyBA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4ZTfcQ2vK9z6M4WF; Fri, 4 Apr 2025 21:30:30 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id 3C3B2140682; Fri, 4 Apr 2025 21:34:12 +0800 (CST) Received: from localhost (10.203.177.66) by frapeml500008.china.huawei.com (7.182.85.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 4 Apr 2025 15:34:10 +0200 Date: Fri, 4 Apr 2025 14:34:09 +0100 From: Jonathan Cameron To: Terry Bowman CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v3 3/4] dax/mum: Save the dax mum platform device pointer Message-ID: <20250404143409.00000961@huawei.com> In-Reply-To: <20250403183315.286710-4-terry.bowman@amd.com> References: <20250403183315.286710-1-terry.bowman@amd.com> <20250403183315.286710-4-terry.bowman@amd.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-pm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml100004.china.huawei.com (7.191.162.219) To frapeml500008.china.huawei.com (7.182.85.71) On Thu, 3 Apr 2025 13:33:14 -0500 Terry Bowman wrote: > From: Nathan Fontenot mum? > > In order to handle registering hmem devices for SOFT RESERVE > resources after the dax hmem device initialization occurs > we need to save a reference to the dax hmem platform device > that will be used in a following patch. > > Saving the platform device pointer also allows us to clean > up the walk_hmem_resources() routine to no require the > struct device argument. > > There should be no functional changes. > > Signed-off-by: Nathan Fontenot > Signed-off-by: Terry Bowman