[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6584bd663bd30_576052949c@iweiny-mobl.notmuch>
Date: Thu, 21 Dec 2023 14:34:14 -0800
From: Ira Weiny <ira.weiny@...el.com>
To: Ira Weiny <ira.weiny@...el.com>, Randy Dunlap <rdunlap@...radead.org>,
<linux-kernel@...r.kernel.org>
CC: Randy Dunlap <rdunlap@...radead.org>, Dan Williams
<dan.j.williams@...el.com>, Vishal Verma <vishal.l.verma@...el.com>, "Dave
Jiang" <dave.jiang@...el.com>, Ira Weiny <ira.weiny@...el.com>,
<nvdimm@...ts.linux.dev>
Subject: Re: [PATCH 2/3] nvdimm/dimm_devs: fix kernel-doc for function params
Ira Weiny wrote:
> Randy Dunlap wrote:
[snip]
> > diff -- a/drivers/nvdimm/dimm_devs.c b/drivers/nvdimm/dimm_devs.c
> > --- a/drivers/nvdimm/dimm_devs.c
> > +++ b/drivers/nvdimm/dimm_devs.c
> > @@ -53,7 +53,10 @@ static int validate_dimm(struct nvdimm_d
> >
> > /**
> > * nvdimm_init_nsarea - determine the geometry of a dimm's namespace area
> > - * @nvdimm: dimm to initialize
> > + * @ndd: dimm to initialize
> > + *
> > + * Returns: %0 if the area is already valid, -errno on error,
>
> This is good...
>
> > ...otherwise an
> > + * ND_CMD_* status code.
>
> I don't see where any of the ->ndctl() calls return an ND_CMD_* status
> code. What am I missing?
If you agree that this should be dropped I can clean it up as I'm trying
to prep the nvdimm tree now and was hoping to take this series.
Ira
>
> The rest looks good,
> Ira
Powered by blists - more mailing lists