linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20170626 build: 1 failures 1 warnings (next-20170626)
Date: Tue, 27 Jun 2017 09:36:09 +0200	[thread overview]
Message-ID: <CAK8P3a31MDiyhvDhyfRG0EZFG7VfUpsy1J-=cJePHefvtWfadQ@mail.gmail.com> (raw)
In-Reply-To: <1498481507.6075.10.camel@mtkswgap22>

On Mon, Jun 26, 2017 at 2:51 PM, Ryder Lee <ryder.lee@mediatek.com> wrote:
> 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?

It's really something that Bjorn needs to fix by applying your patch,
but if he's currently not able to do that for some reason, a possible
workaround would be for either Stephen Rothwell to apply your fixup
on linux-next, or Andrew Morton to add it to his mmotm tree, either
way it will be part of linux-next and on top of the pci-next tree,
until Bjorn applies it.

Please re-send your patch to both of them, with Bjorn on Cc.

        Arnd

  reply	other threads:[~2017-06-27  7:36 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
2017-06-27  7:36     ` Arnd Bergmann [this message]
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='CAK8P3a31MDiyhvDhyfRG0EZFG7VfUpsy1J-=cJePHefvtWfadQ@mail.gmail.com' \
    --to=arnd@arndb.de \
    --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).