[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231016150804.000054aa@Huawei.com>
Date: Mon, 16 Oct 2023 15:08:04 +0100
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Terry Bowman <Terry.Bowman@....com>
CC: Robert Richter <rrichter@....com>,
Alison Schofield <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>,
"Ira Weiny" <ira.weiny@...el.com>,
Ben Widawsky <bwidawsk@...nel.org>,
"Dan Williams" <dan.j.williams@...el.com>,
Davidlohr Bueso <dave@...olabs.net>,
Dave Jiang <dave.jiang@...el.com>, <linux-cxl@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [PATCH v11 10/20] cxl/pci: Introduce config option PCIEAER_CXL
> >>> diff --git a/drivers/cxl/mem.c b/drivers/cxl/mem.c
> >>> index 04107058739b..61ca21c020fa 100644
> >>> --- a/drivers/cxl/mem.c
> >>> +++ b/drivers/cxl/mem.c
> >>> @@ -157,6 +157,8 @@ static int cxl_mem_probe(struct device *dev)
> >>> else
> >>> endpoint_parent = &parent_port->dev;
> >>>
> >>> + devm_cxl_setup_parent_dport(dev, dport);
> >>
> >> devm calls can always fail (because if nothing else you have to register
> >> some cleanup and that involves an allocation. If you want to ignore
> >> that I'd expect a comment here.
> >>
> >
> > We will add error handling here.
> >
> > Regards,
> > Terry
> >
>
> Found devm_cxl_setup_parent_dport() is a NULL function without return value.
Hmm. Then it's not a devm function.
I went looking and can't find it registering any cleanup so
just rename it to cxl_setup_parent_dport()
>
> Regards,
> Terry
Powered by blists - more mailing lists