From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Dilip Kota <eswara.kota@linux.intel.com>,
linux-pci@vger.kernel.org, gustavo.pimentel@synopsys.com,
andrew.murray@arm.com, linux-kernel@vger.kernel.org,
andriy.shevchenko@intel.com, rdunlap@infradead.org,
cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com,
qi-ming.wu@intel.com
Subject: Re: [PATCH v1 0/1]Fix build warning and errors
Date: Thu, 28 Nov 2019 08:46:06 -0600 [thread overview]
Message-ID: <20191128144606.GA260904@google.com> (raw)
In-Reply-To: <20191128101954.GA30478@e121166-lin.cambridge.arm.com>
On Thu, Nov 28, 2019 at 10:19:55AM +0000, Lorenzo Pieralisi wrote:
> [+Bjorn]
>
> On Thu, Nov 28, 2019 at 04:31:12PM +0800, Dilip Kota wrote:
> > Mark Intel PCIe driver depends on MSI IRQ Domain to fix
> > the below warnings and respective build errors.
> >
> > WARNING: unmet direct dependencies detected for PCIE_DW_HOST
> > Depends on [n]: PCI [=y] && PCI_MSI_IRQ_DOMAIN [=n]
> > Selected by [y]:
> > - PCIE_INTEL_GW [=y] && PCI [=y] && OF [=y] && (X86 [=y] || COMPILE_TEST [=n])
>
> I don't know yet if we fix it up or I drop the series, given how
> late this is in the release cycle and very short time this code
> has been in -next.
I think given the timing and the holiday we need to drop it for now.
next prev parent reply other threads:[~2019-11-28 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 8:31 [PATCH v1 0/1]Fix build warning and errors Dilip Kota
2019-11-28 8:31 ` [PATCH v1 1/1] PCI: dwc: Kconfig: Mark intel PCIe driver depends on MSI IRQ Domain Dilip Kota
2019-11-28 18:18 ` Randy Dunlap
2019-11-28 10:19 ` [PATCH v1 0/1]Fix build warning and errors Lorenzo Pieralisi
2019-11-28 14:46 ` Bjorn Helgaas [this message]
2019-12-05 16:23 ` Lorenzo Pieralisi
2019-12-06 6:35 ` Dilip Kota
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=20191128144606.GA260904@google.com \
--to=helgaas@kernel.org \
--cc=andrew.murray@arm.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=eswara.kota@linux.intel.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=qi-ming.wu@intel.com \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.