Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: "Jon Mason" <jdmason@kudzu.us>,
	"Dave Jiang" <dave.jiang@intel.com>,
	"Allen Hubbe" <allenbh@gmail.com>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	ntb@lists.linux.dev, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] PCI: endpoint: pci-epf-vntb: return an error code on bar init
Date: Mon, 19 May 2025 17:12:19 -0400	[thread overview]
Message-ID: <aCues6UrqlV0pDfw@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250505-pci-vntb-bar-mapping-v1-1-0e0d12b2fa71@baylibre.com>

On Mon, May 05, 2025 at 07:41:47PM +0200, Jerome Brunet wrote:

subject: s/return/Return

> According the function documentation of epf_ntb_init_epc_bar(),
> the function should return an error code on error. However, it
> returns -1 when no BAR is available.
>
> Return -EINVAL instead.
>
> Fixes: e35f56bb0330 ("PCI: endpoint: Support NTB transfer between RC and EP")
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>

After fix above small issue about subject.

Reviewed-by: Frank Li <Frank.Li@nxp.com>

> ---
>  drivers/pci/endpoint/functions/pci-epf-vntb.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/endpoint/functions/pci-epf-vntb.c b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> index e4da3fdb000723e3adad01f0ddf230ecc0e572a7..35fa0a21fc91100a5539bff775e7ebc25e1fb9c1 100644
> --- a/drivers/pci/endpoint/functions/pci-epf-vntb.c
> +++ b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> @@ -680,7 +680,7 @@ static int epf_ntb_init_epc_bar(struct epf_ntb *ntb)
>  		barno = pci_epc_get_next_free_bar(epc_features, barno);
>  		if (barno < 0) {
>  			dev_err(dev, "Fail to get NTB function BAR\n");
> -			return barno;
> +			return -EINVAL;
>  		}
>  		ntb->epf_ntb_bar[bar] = barno;
>  	}
>
> --
> 2.47.2
>

  reply	other threads:[~2025-05-19 21:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 17:41 [PATCH 0/4] PCI: endpoint: pci-epf-vntb: allow arbitrary BAR mapping Jerome Brunet
2025-05-05 17:41 ` [PATCH 1/4] PCI: endpoint: pci-epf-vntb: return an error code on bar init Jerome Brunet
2025-05-19 21:12   ` Frank Li [this message]
2025-05-05 17:41 ` [PATCH 2/4] PCI: endpoint: pci-epf-vntb: align mw naming with config names Jerome Brunet
2025-05-19 21:21   ` Frank Li
2025-05-20  7:47     ` Jerome Brunet
2025-05-21 16:28       ` Frank Li
2025-05-21 16:42         ` Jerome Brunet
2025-05-05 17:41 ` [PATCH 3/4] PCI: endpoint: pci-epf-vntb: allow arbitrary BAR configuration Jerome Brunet
2025-05-19 22:29   ` Frank Li
2025-05-20  8:06     ` Jerome Brunet
2025-05-20 17:08       ` Frank Li
2025-05-05 17:41 ` [PATCH 4/4] NTB: epf: Allow arbitrary BAR mapping Jerome Brunet
2025-05-19 22:44   ` Frank Li
2025-05-20  8:11     ` Jerome Brunet

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=aCues6UrqlV0pDfw@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=allenbh@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dave.jiang@intel.com \
    --cc=jbrunet@baylibre.com \
    --cc=jdmason@kudzu.us \
    --cc=kishon@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=ntb@lists.linux.dev \
    /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