linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczy��ski" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Xiaowei Song" <songxiaowei@huawei.com>,
	stable@vger.kernel.org
Subject: Ping: [PATCH] PCI: kirin: Select REGMAP_MMIO for PCIE_KIRIN
Date: Tue, 07 Mar 2023 13:42:01 +0800	[thread overview]
Message-ID: <8996e9ba32cbdc24b828c9a37793b39f17eb33a8.camel@xry111.site> (raw)
In-Reply-To: <20230228043423.19335-1-xry111@xry111.site>

Gentle ping.

On Tue, 2023-02-28 at 12:34 +0800, Xi Ruoyao wrote:
> pcie-kirin.c invokes devm_regmap_init_mmio, so it's necessary to
> select
> REGMAP_MMIO or vmlinux fails to link with "undefined reference to
> `__devm_regmap_init_mmio_clk`.
> 
> Cc: stable@vger.kernel.org # at least for 6.1 and 6.2
> Signed-off-by: Xi Ruoyao <xry111@xry111.site>
> ---
>  drivers/pci/controller/dwc/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/pci/controller/dwc/Kconfig
> b/drivers/pci/controller/dwc/Kconfig
> index 434f6a4f4041..d29551261e80 100644
> --- a/drivers/pci/controller/dwc/Kconfig
> +++ b/drivers/pci/controller/dwc/Kconfig
> @@ -307,6 +307,7 @@ config PCIE_KIRIN
>         tristate "HiSilicon Kirin series SoCs PCIe controllers"
>         depends on PCI_MSI
>         select PCIE_DW_HOST
> +       select REGMAP_MMIO
>         help
>           Say Y here if you want PCIe controller support
>           on HiSilicon Kirin series SoCs.

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-03-07  5:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  4:34 [PATCH] PCI: kirin: Select REGMAP_MMIO for PCIE_KIRIN Xi Ruoyao
2023-03-07  5:42 ` Xi Ruoyao [this message]
2023-03-10 10:45   ` Ping: " Lorenzo Pieralisi
2023-03-10 10:51     ` Xi Ruoyao

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=8996e9ba32cbdc24b828c9a37793b39f17eb33a8.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=robh@kernel.org \
    --cc=songxiaowei@huawei.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).