public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: dlemoal@kernel.org, linux-pci@vger.kernel.org
Subject: Re: [bug report] PCI: endpoint: Automatically create a function specific attributes group
Date: Sun, 14 May 2023 19:06:52 +0530	[thread overview]
Message-ID: <20230514133652.GA116991@thinkpad> (raw)
In-Reply-To: <95d23290-496a-462c-87c5-944df1e20ba1@kili.mountain>

On Thu, May 11, 2023 at 10:06:40AM +0300, Dan Carpenter wrote:
> Hello Damien Le Moal,
> 
> The patch 01c68988addf: "PCI: endpoint: Automatically create a
> function specific attributes group" from Apr 15, 2023, leads to the
> following Smatch static checker warning:
> 
> 	drivers/pci/endpoint/pci-ep-cfs.c:540 pci_ep_cfs_add_type_group()
> 	warn: 'group' isn't an ERR_PTR
> 
> drivers/pci/endpoint/pci-ep-cfs.c
>     532 static void pci_ep_cfs_add_type_group(struct pci_epf_group *epf_group)
>     533 {
>     534         struct config_group *group;
>     535 
>     536         group = pci_epf_type_add_cfs(epf_group->epf, &epf_group->group);
>     537         if (!group)
>     538                 return;
>     539 
> --> 540         if (IS_ERR(group)) {
> 
> pci_epf_type_add_cfs() does not return error pointers currently.  Which
> is fine.  Presumably it will start returning them later.  But could you
> add some comments next to the pci_epf_type_add_cfs() to explain what a
> NULL return means vs an error pointer return?
> 

pci_epf_type_add_cfs() may return ERR_PTR from add_cfs() callback.

Regarding comments, it should be added as a part of kdoc for
pci_epf_type_add_cfs(). It already does for NULL part but not for ERR_PTR.

- Mani

>     541                 dev_err(&epf_group->epf->dev,
>     542                         "failed to create epf type specific attributes\n");
>     543                 return;
>     544         }
>     545 
>     546         configfs_register_group(&epf_group->group, group);
>     547 }
> 
> regards,
> dan carpenter

-- 
மணிவண்ணன் சதாசிவம்

  reply	other threads:[~2023-05-14 13:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  7:06 [bug report] PCI: endpoint: Automatically create a function specific attributes group Dan Carpenter
2023-05-14 13:36 ` Manivannan Sadhasivam [this message]
2023-05-14 20:12   ` Dan Carpenter
2023-05-15  4:22     ` Manivannan Sadhasivam
2023-05-15  2:14   ` Damien Le Moal
2023-05-15  4:21     ` Manivannan Sadhasivam

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=20230514133652.GA116991@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=dan.carpenter@linaro.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-pci@vger.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