[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6940797de4c26_1cee1004e@dwillia2-mobl4.notmuch>
Date: Mon, 15 Dec 2025 13:11:25 -0800
From: <dan.j.williams@...el.com>
To: Alejandro Lucero Palau <alucerop@....com>, Dan Williams
<dan.j.williams@...el.com>, <dave.jiang@...el.com>
CC: <linux-cxl@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<Smita.KoralahalliChannabasappa@....com>, <alison.schofield@...el.com>,
<terry.bowman@....com>, <alejandro.lucero-palau@....com>,
<linux-pci@...r.kernel.org>, <Jonathan.Cameron@...wei.com>, Shiju Jose
<shiju.jose@...wei.com>
Subject: Re: [PATCH 1/6] cxl/mem: Fix devm_cxl_memdev_edac_release() confusion
Alejandro Lucero Palau wrote:
>
> On 12/4/25 02:21, Dan Williams wrote:
> > A device release method is only for undoing allocations on the path to
> > preparing the device for device_add(). In contrast, devm allocations are
>
>
> Should this not be referencing to device_del() instead?
No, device_del() is not involved in what this patch is addressing. Prior
to device_add() the container of that device is allocated and acquires
some resources. device_add() and device_del() are only registering /
unregistering the device with the device-core. The release method undoes
any resource acquisition done *prior* to device_add().
Powered by blists - more mailing lists