From: Dilip Kota <eswara.kota@linux.intel.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: 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: Fri, 6 Dec 2019 14:35:54 +0800 [thread overview]
Message-ID: <0bc42fb8-4ff5-4ecf-ddf4-305de2186efc@linux.intel.com> (raw)
In-Reply-To: <20191205162356.GA19365@e121166-lin.cambridge.arm.com>
On 12/6/2019 12:23 AM, Lorenzo Pieralisi wrote:
> 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])
>>
>> Dilip Kota (1):
>> PCI: dwc: Kconfig: Mark intel PCIe driver depends on MSI IRQ Domain
>>
>> drivers/pci/controller/dwc/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
> Hi Dilip,
>
> would you mind squashing this patch into the initial series and repost
> it (rebase it against current mainline) straight away ? I will
> rebase it to -rc1 and push it out next week (I am asking since then
> I am afk for a month so I would like to get your code queued asap,
> it is ready).
Sure, i will do it.
Thanks for prioritizing.
Regards,
Dilip
>
> Thanks,
> Lorenzo
prev parent reply other threads:[~2019-12-06 6:36 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
2019-12-05 16:23 ` Lorenzo Pieralisi
2019-12-06 6:35 ` Dilip Kota [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=0bc42fb8-4ff5-4ecf-ddf4-305de2186efc@linux.intel.com \
--to=eswara.kota@linux.intel.com \
--cc=andrew.murray@arm.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@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 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).