From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Evan Green <evgreen@chromium.org>
Cc: agross@codeaurora.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org,
Karthikeyan Ramasubramanian <kramasub@codeaurora.org>,
Sagar Dharia <sdharia@codeaurora.org>,
Girish Mahadevan <girishm@codeaurora.org>,
groeck@chromium.org
Subject: Re: linux-next: build failure after merge of the qcom tree
Date: Thu, 26 Apr 2018 14:52:55 +1000 [thread overview]
Message-ID: <20180426145255.0141300e@canb.auug.org.au> (raw)
In-Reply-To: <CAE=gft6e6wo1nj+Rw5=f+UXxhx3Hof7Nt=E9+-OAzvvv8Gct1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Hi Evan,
On Thu, 26 Apr 2018 03:39:25 +0000 Evan Green <evgreen@chromium.org> wrote:
>
> Guenter and I had a fix for compile test here, which had failures that
> looked similar:
>
> https://lkml.org/lkml/2018/4/18/752
That looks like it could very well be the problem/solution.
> I was hoping to verify myself whether or not this fixed allmodconfig, but
> my machine at home is not so fast, and I must be missing something, either
> in the configuration or the tree. Which tree exactly are you building?
I was attempting to compile my partial linux-next for today after
merging the qcom tree. So once I release linux-next, it will be commit
a72d0aa48d2e ("Merge remote-tracking branch 'omap/for-next'") plus a
merge of the qcom tree
(git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git#for-next
- which today meant commit c78d6951a806 ("Merge branch 'soc-for-4.18'
into all-for-4.18")).
I suspect that just Linus' tree merged with the qcom tree would have
been enough to cause the failure.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-26 4:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 22:40 linux-next: build failure after merge of the qcom tree Stephen Rothwell
2018-04-26 3:39 ` Evan Green
2018-04-26 4:52 ` Stephen Rothwell [this message]
2018-04-26 16:42 ` Evan Green
2018-04-26 21:23 ` Andy Gross
-- strict thread matches above, loose matches on Subject: below --
2023-12-03 23:30 Stephen Rothwell
2023-12-03 23:23 Stephen Rothwell
2023-09-20 22:42 Stephen Rothwell
2023-09-21 6:30 ` Luca Weiss
2022-11-07 22:00 Stephen Rothwell
2022-11-07 22:15 ` Matti Lehtimäki
2022-11-08 1:30 ` Bjorn Andersson
2021-10-24 23:43 Stephen Rothwell
2021-10-25 2:37 ` Bjorn Andersson
2020-04-15 0:41 Stephen Rothwell
2020-04-15 1:18 ` John Stultz
2020-04-20 23:29 ` Stephen Rothwell
2020-04-21 2:41 ` John Stultz
2020-05-18 5:16 ` Stephen Rothwell
2020-05-18 6:19 ` Bjorn Andersson
2019-04-23 23:25 Stephen Rothwell
2019-04-23 23:50 ` Matthias Kaehlcke
2016-03-31 23:28 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=20180426145255.0141300e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agross@codeaurora.org \
--cc=evgreen@chromium.org \
--cc=girishm@codeaurora.org \
--cc=groeck@chromium.org \
--cc=kramasub@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sdharia@codeaurora.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).