From: ryder.lee@mediatek.com (Ryder Lee)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20170626 build: 1 failures 1 warnings (next-20170626)
Date: Mon, 26 Jun 2017 20:51:47 +0800 [thread overview]
Message-ID: <1498481507.6075.10.camel@mtkswgap22> (raw)
In-Reply-To: <20170626115653.e4xs4lk4paibuphx@sirena.org.uk>
On Mon, 2017-06-26 at 12:56 +0100, Mark Brown wrote:
> 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.
Hi Mark,
This is due to we are in different branch but merge together...
Anyway, I could send a critical patch, but I need Bjorn help to apply to
-next. Seems he didn't response these days.
Not sure how could I send it?
Ryder.
next prev parent reply other threads:[~2017-06-26 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1dPPgG-0002pe-3A@optimist>
2017-06-26 11:56 ` next-20170626 build: 1 failures 1 warnings (next-20170626) Mark Brown
2017-06-26 12:51 ` Ryder Lee [this message]
2017-06-27 7:36 ` Arnd Bergmann
2017-06-27 9:21 ` Ryder Lee
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=1498481507.6075.10.camel@mtkswgap22 \
--to=ryder.lee@mediatek.com \
--cc=linux-arm-kernel@lists.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).