From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof's autobuilder <build@lixom.net>,
Ohad Ben-Cohen <ohad@wizery.com>,
linux-remoteproc@vger.kernel.org, Olof Johansson <olof@lixom.net>,
kernel-build-reports@lists.linaro.org
Subject: Re: mainline build: 9 warnings 1 failures (mainline/v4.10-7345-g5bcbe22)
Date: Thu, 23 Feb 2017 15:05:55 -0800 [thread overview]
Message-ID: <20170223230555.GI23255@minitux> (raw)
In-Reply-To: <CAK8P3a0TB4SdixX+Gk__uZRqSwpO-v-JwKOR747uhCi=EjtqVA@mail.gmail.com>
On Thu 23 Feb 13:01 PST 2017, Arnd Bergmann wrote:
> On Thu, Feb 23, 2017 at 9:48 PM, Olof's autobuilder <build@lixom.net> wrote:
>
> > Errors:
> >
> > arm.allmodconfig:
> > /work/build/batch/drivers/soc/ti/wkup_m3_ipc.c:373:36: error: 'struct rproc' has no member named 'firmware_loading_complete'
>
> This apparently just broke after Linus pulled the remoteproc git tree. I had not
> seen this failure in linux-next yet. Maybe a dependency that wasn't
> handled right,
> or a broken last-minute patch?
>
The commit 2099c77d4af7 ("remoteproc: Drop firmware_loading_complete")
depends on 36cc9fd9ce0f ("soc: ti: wkup_m3_ipc: Drop wait from
wkup_m3_rproc_boot_thread"), but I apparently missed this.
The first patch was part of my pull for v4.11 and the latter was picked
up by Tony and is merged by Olof into one of your trees. I should
probably have taken both through my tree...
Sorry about this.
Regards,
Bjorn
prev parent reply other threads:[~2017-02-23 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58af4aa2.8a12620a.c3a2b.698b@mx.google.com>
2017-02-23 21:01 ` mainline build: 9 warnings 1 failures (mainline/v4.10-7345-g5bcbe22) Arnd Bergmann
2017-02-23 23:05 ` Bjorn Andersson [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=20170223230555.GI23255@minitux \
--to=bjorn.andersson@linaro.org \
--cc=arnd@arndb.de \
--cc=build@lixom.net \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=olof@lixom.net \
/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