netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zijun Hu <zijun_hu@icloud.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Uwe Kleine-König" <ukleinek@kernel.org>,
	"James Bottomley" <James.Bottomley@hansenpartnership.com>,
	"Thomas Weißschuh" <thomas@t-8ch.de>,
	linux-kernel@vger.kernel.org, nvdimm@lists.linux.dev,
	linux-sound@vger.kernel.org, sparclinux@vger.kernel.org,
	linux-block@vger.kernel.org, linux-cxl@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net, arm-scmi@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-gpio@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	linux-mediatek@lists.infradead.org, linux-hwmon@vger.kernel.org,
	linux-media@vger.kernel.org, linux-pwm@vger.kernel.org,
	linux-remoteproc@vger.kernel.org, linux-scsi@vger.kernel.org,
	open-iscsi@googlegroups.com, linux-usb@vger.kernel.org,
	linux-serial@vger.kernel.org, netdev@vger.kernel.org,
	"Zijun Hu" <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH v3 10/11] cxl/pmem: Remove match_nvdimm_bridge()
Date: Fri, 6 Dec 2024 09:02:58 +0800	[thread overview]
Message-ID: <9d2de147-8fc6-419f-bf3e-03f6b86cbb44@icloud.com> (raw)
In-Reply-To: <Z1It83v8xuNuLrOt@aschofie-mobl2.lan>

On 2024/12/6 06:49, Alison Schofield wrote:
> On Thu, Dec 05, 2024 at 08:10:19AM +0800, Zijun Hu wrote:
>> From: Zijun Hu <quic_zijuhu@quicinc.com>
> 
> Suggest conveying more detail in the commit msg:
> 
> cxl/pmem> Replace match_nvdimm_bridge() w device_match_type()
> 

good suggestions
will take it in v4.

>>
>> match_nvdimm_bridge(), as matching function of device_find_child(), is to
>> match a device with device type @cxl_nvdimm_bridge_type, and is unnecessary
> 
> Prefer being clear that this function recently become needless.
> Something like:
> 
> match_nvdimm_bridge(), as matching function of device_find_child(),
> matches a device with device type @cxl_nvdimm_bridge_type. The recently
> added API, device_match_type, simplifies that task.
>  
> Replace match_nvdimm_bridge() usage with device_match_type().
> 

sure. will do it in v4 by following these good comments.

> With that you can add:
> 
> Reviewed-by: Alison Schofield <alison.schofield@intel.com>
> 
>>
>> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
>> ---
>>  drivers/cxl/core/pmem.c | 9 +++------
>>  1 file changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/cxl/core/pmem.c b/drivers/cxl/core/pmem.c
>> index a8473de24ebfd92f12f47e0556e28b81a29cff7c..0f8166e793e14fc0b1c04ffda79e756a743d9e6b 100644
>> --- a/drivers/cxl/core/pmem.c
>> +++ b/drivers/cxl/core/pmem.c
>> @@ -57,11 +57,6 @@ bool is_cxl_nvdimm_bridge(struct device *dev)
>>  }
>>  EXPORT_SYMBOL_NS_GPL(is_cxl_nvdimm_bridge, "CXL");
>>  
>> -static int match_nvdimm_bridge(struct device *dev, const void *data)
>> -{
>> -	return is_cxl_nvdimm_bridge(dev);
>> -}
>> -
>>  /**
>>   * cxl_find_nvdimm_bridge() - find a bridge device relative to a port
>>   * @port: any descendant port of an nvdimm-bridge associated
>> @@ -75,7 +70,9 @@ struct cxl_nvdimm_bridge *cxl_find_nvdimm_bridge(struct cxl_port *port)
>>  	if (!cxl_root)
>>  		return NULL;
>>  
>> -	dev = device_find_child(&cxl_root->port.dev, NULL, match_nvdimm_bridge);
>> +	dev = device_find_child(&cxl_root->port.dev,
>> +				&cxl_nvdimm_bridge_type,
>> +				device_match_type);
>>  
>>  	if (!dev)
>>  		return NULL;
>>
>> -- 
>> 2.34.1
>>
>>


  reply	other threads:[~2024-12-06  1:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  0:10 [PATCH v3 00/11] driver core: Constify API device_find_child() Zijun Hu
2024-12-05  0:10 ` [PATCH v3 01/11] libnvdimm: Simplify nd_namespace_store() implementation Zijun Hu
2024-12-05 23:30   ` Alison Schofield
2024-12-06  0:56     ` Zijun Hu
2024-12-05  0:10 ` [PATCH v3 02/11] slimbus: core: Constify slim_eaddr_equal() Zijun Hu
2024-12-05  0:10 ` [PATCH v3 03/11] bus: fsl-mc: Constify fsl_mc_device_match() Zijun Hu
2024-12-05  0:10 ` [PATCH v3 04/11] driver core: Constify API device_find_child() then adapt for various usages Zijun Hu
2024-12-05 10:41   ` Uwe Kleine-König
2024-12-05 13:16     ` Zijun Hu
2024-12-05 22:39   ` Alison Schofield
2024-12-06  7:21   ` Uwe Kleine-König
2024-12-06 11:08     ` Zijun Hu
2024-12-06 13:52   ` Takashi Sakamoto
2024-12-08 13:18     ` Zijun Hu
2024-12-05  0:10 ` [PATCH v3 05/11] driver core: Simplify API device_find_child_by_name() implementation Zijun Hu
2024-12-05  0:10 ` [PATCH v3 06/11] driver core: Remove match_any() Zijun Hu
2024-12-05  0:10 ` [PATCH v3 07/11] slimbus: core: Simplify of_find_slim_device() implementation Zijun Hu
2024-12-05  0:10 ` [PATCH v3 08/11] gpio: sim: Remove gpio_sim_dev_match_fwnode() Zijun Hu
2024-12-05  8:10   ` Uwe Kleine-König
2024-12-05  8:37     ` quic_zijuhu
2024-12-05 10:37       ` Uwe Kleine-König
2024-12-05 13:19         ` Zijun Hu
2024-12-05 16:24   ` Bartosz Golaszewski
2024-12-06  1:00     ` Zijun Hu
2024-12-05  0:10 ` [PATCH v3 09/11] driver core: Introduce an device matching API device_match_type() Zijun Hu
2024-12-05  0:10 ` [PATCH v3 10/11] cxl/pmem: Remove match_nvdimm_bridge() Zijun Hu
2024-12-05 22:49   ` Alison Schofield
2024-12-06  1:02     ` Zijun Hu [this message]
2024-12-05  0:10 ` [PATCH v3 11/11] usb: typec: class: Remove both cable_match() and partner_match() Zijun Hu
2024-12-05  0:31 ` [PATCH v3 00/11] driver core: Constify API device_find_child() Zijun Hu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9d2de147-8fc6-419f-bf3e-03f6b86cbb44@icloud.com \
    --to=zijun_hu@icloud.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alison.schofield@intel.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=open-iscsi@googlegroups.com \
    --cc=quic_zijuhu@quicinc.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=thomas@t-8ch.de \
    --cc=ukleinek@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).