From: Ryder Lee <ryder.lee@mediatek.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>
Subject: [RESEND PATCH] critical patch to fix pci-tree build bot failure
Date: Tue, 27 Jun 2017 17:24:10 +0800 [thread overview]
Message-ID: <1498555451-55073-1-git-send-email-ryder.lee@mediatek.com> (raw)
Hi Stephen and Andrew,
Could you help to apply this patch? Seems Bjorn didn't response it these days.
This patch(based on pci-next tree) will fix the following build bot failure:
>> On Mon, Jun 26, 2017 at 09:47:36AM +0100, Build bot for Mark Brown wrote:
>>
>> This build failure is still present in -next:
>>
>> > arm-allmodconfig
>> > ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit
>> > declaration of function 'pci_register_host_bridge'
>> > [-Werror=implicit-function-declaration]
>>
>> and we're at -rc7 now.
This is because pci/host-mediatek is a seperate branch in pci-tree, but merge together without proper modifications(eg. some API changes).
Hi Bjorn,
I rewrote commit message. Please ignore my previous one, sorry for inconvenience.
Thanks a lot!
Ryder Lee (1):
PCI: mediatek: change to use the new host bridge interface
drivers/pci/host/pcie-mediatek.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--
1.9.1
next reply other threads:[~2017-06-27 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 9:24 Ryder Lee [this message]
2017-06-27 9:24 ` [PATCH] PCI: mediatek: change to use the new host bridge interface Ryder Lee
2017-06-27 22:30 ` Bjorn Helgaas
2017-06-27 23:20 ` Bjorn Helgaas
2017-06-28 1:21 ` Ryder Lee
2017-06-27 13:20 ` [RESEND PATCH] critical patch to fix pci-tree build bot failure Bjorn Helgaas
2017-06-27 22:10 ` Stephen Rothwell
2017-06-27 22:23 ` Bjorn Helgaas
2017-06-28 20:43 ` Bjorn Helgaas
2017-06-28 21:55 ` Stephen Rothwell
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=1498555451-55073-1-git-send-email-ryder.lee@mediatek.com \
--to=ryder.lee@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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
Powered by JetHome