linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samiksha Garg <samikshagarg@google.com>
To: Hans Zhang <18255117159@163.com>
Cc: jingoohan1@gmail.com, manivannan.sadhasivam@linaro.org,
	ajayagarwal@google.com, maurora@google.com,
	linux-pci@vger.kernel.org, manugautam@google.com
Subject: Re: [PATCH] PCI: dwc: EXPORT dw_pcie_allocate_domains
Date: Tue, 27 May 2025 04:42:22 +0000	[thread overview]
Message-ID: <aDVCronBm32GwF77@google.com> (raw)
In-Reply-To: <39743267-6a2c-4a5a-9581-05b03e25477f@163.com>

Hi,
Yes I understand that `pci-keystone` is currently built in,
which is why it can use `dw_pcie_allocate_domains` without
the need for symbol export.

My intent with the patch was to make this API accessible to
other out-of-tree drivers that rely on the Designware core
and might have similar want as `pci-keystone`.

Since `dw_pcie_allocate_domains` is already non-static,
exporting it could enable consistent reuse without requiring
duplication or workarounds.

Thanks,
Samiksha

On Tue, May 27, 2025 at 12:29:18AM +0800, Hans Zhang wrote:
> 
> 
> On 2025/5/26 18:42, Samiksha Garg wrote:
> > Hi Mani,
> > Thanks for your response. I can see that pci-keystone driver already calls this function.
> > Does it not mean that there is already an upstream user?
> > 
> 
> Hello,
> 
> pci-keystone is build-in.
> 
> Best regards,
> Hans
> 

  reply	other threads:[~2025-05-27  4:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 10:42 [PATCH] PCI: dwc: EXPORT dw_pcie_allocate_domains Samiksha Garg
2025-05-26 11:20 ` Manivannan Sadhasivam
2025-05-26 16:04   ` Samiksha Garg
2025-05-28  3:45     ` Manivannan Sadhasivam
2025-05-26 16:26 ` Hans Zhang
2025-05-26 16:29 ` Hans Zhang
2025-05-27  4:42   ` Samiksha Garg [this message]
2025-05-27  5:49     ` Hans Zhang
2025-05-27  8:09       ` Christoph Hellwig

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=aDVCronBm32GwF77@google.com \
    --to=samikshagarg@google.com \
    --cc=18255117159@163.com \
    --cc=ajayagarwal@google.com \
    --cc=jingoohan1@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=manugautam@google.com \
    --cc=maurora@google.com \
    /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;
as well as URLs for NNTP newsgroup(s).