From: Ryder Lee <ryder.lee@mediatek.com>
To: Mark Brown <broonie@kernel.org>,
LorenzoPieralisi <lorenzo.pieralisi@arm.com>
Cc: "linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"kernel-build-reports@lists.linaro.org"
<kernel-build-reports@lists.linaro.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: next-20170621 build: 1 failures 7 warnings (next-20170621)
Date: Fri, 23 Jun 2017 17:13:16 +0800 [thread overview]
Message-ID: <1498209196.26313.71.camel@mtkswgap22> (raw)
In-Reply-To: <20170621100440.vcaxagg4yjca2cv4@sirena.org.uk>
Sorry for late reply,
+Lorenzo
On Wed, 2017-06-21 at 18:04 +0800, Mark Brown wrote:
> On Wed, Jun 21, 2017 at 10:56:07AM +0100, Build bot for Mark Brown wrote:
>
> Today's -next fails to build an arm allmodconfig due to:
>
> > arm-allmodconfig
> > ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration]
>
> caused by eaf3023b0498a (PCI: mediatek: Add MediaTek PCIe host
> controller support).
Hi Lorenzo,
I picked up your changes and had some modifications like what you did
for other platforms:
9f8e3a5 PCI: Add devm_pci_alloc_host_bridge() interface
35a1a84 PCI: Add pci_free_host_bridge() interface
e33aafd PCI: Initialize bridge release function at bridge allocation
...and it looks Okay.
I have also noticed that you continue sending patches for other
platforms but I have not yet had a look in detail. I'm quite busy these
days and don't have time to dig it, hence it is becoming a little
unmanageable for me.
Did you have a chance to send the same patches for MediaTek? I
appreciate that and I can help to test it on our platforms.
Ryder.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-06-23 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1dNcMp-0005RN-1w@optimist>
2017-06-21 10:04 ` next-20170621 build: 1 failures 7 warnings (next-20170621) Mark Brown
2017-06-23 9:13 ` Ryder Lee [this message]
2017-06-23 9:43 ` Lorenzo Pieralisi
2017-06-23 10:22 ` Ryder Lee
2017-06-23 11:59 ` Lorenzo Pieralisi
2017-06-27 19:58 ` Bjorn Helgaas
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=1498209196.26313.71.camel@mtkswgap22 \
--to=ryder.lee@mediatek.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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).