From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
linux-pci <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: linux-next: Tree for Nov 30 (drivers/pci/controller/dwc/pcie-designware-host.c)
Date: Tue, 1 Dec 2020 14:27:57 +0100 [thread overview]
Message-ID: <8b81ba16-7493-ddd2-65ac-b1ac46537deb@samsung.com> (raw)
In-Reply-To: <20201201113412.GA2389@e121166-lin.cambridge.arm.com>
Hi
On 01.12.2020 12:34, Lorenzo Pieralisi wrote:
> On Mon, Nov 30, 2020 at 08:44:55PM -0800, Randy Dunlap wrote:
>> On 11/30/20 12:36 AM, Stephen Rothwell wrote:
>>> Changes since 20201127:
>> on x86_64:
>>
>> WARNING: unmet direct dependencies detected for PCIE_DW_HOST
>> Depends on [n]: PCI [=y] && PCI_MSI_IRQ_DOMAIN [=n]
>> Selected by [y]:
>> - PCI_EXYNOS [=y] && PCI [=y] && (ARCH_EXYNOS || COMPILE_TEST [=y])
>
> [...]
>
>> caused by:
>> commit f0a6743028f938cdd34e0c3249d3f0e6bfa04073
>> Author: Jaehoon Chung <jh80.chung@samsung.com>
>> Date: Fri Nov 13 18:01:39 2020 +0100
>>
>> PCI: dwc: exynos: Rework the driver to support Exynos5433 varian
>>
>>
>> which removed "depends on PCI_MSI_IRQ_DOMAIN from config PCI_EXYNOS.
> Fixed up and squashed in the original commit - we should probably rework
> the DWC driver dependencies on PCI_MSI_IRQ_DOMAIN to really fix it, for
> the time being this should do.
Thanks! I wasn't aware of that hidden dependency.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
prev parent reply other threads:[~2020-12-01 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201130193626.1c408e47@canb.auug.org.au>
2020-12-01 4:44 ` linux-next: Tree for Nov 30 (drivers/pci/controller/dwc/pcie-designware-host.c) Randy Dunlap
2020-12-01 11:34 ` Lorenzo Pieralisi
2020-12-01 13:27 ` Marek Szyprowski [this message]
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=8b81ba16-7493-ddd2-65ac-b1ac46537deb@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=bhelgaas@google.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).