From: Andy Gross <andy.gross@linaro.org>
To: Evan Green <evgreen@chromium.org>
Cc: sfr@canb.auug.org.au, 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 16:23:30 -0500 [thread overview]
Message-ID: <20180426212330.GD25699@hector.attlocal.net> (raw)
In-Reply-To: <CAE=gft625-cWjBQXcNRumFRGrmF6nJDf0pAjBbG+gAAS_YXtWg@mail.gmail.com>
On Thu, Apr 26, 2018 at 04:42:17PM +0000, Evan Green wrote:
> > I suspect that just Linus' tree merged with the qcom tree would have
> > been enough to cause the failure.
Sorry for missing this in my testing.
>
>
> I've verified that the patch listed above fixes the issue for me. Andy, if
> it looks okay to you, go ahead an pull it in. Apologies for the trouble,
> and thanks Guenter for having builders that notice this stuff early!
> -Evan
Thanks for looking at this Evan.
Andy
next prev parent reply other threads:[~2018-04-26 21:23 UTC|newest]
Thread overview: 28+ 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
2018-04-26 16:42 ` Evan Green
2018-04-26 21:23 ` Andy Gross [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 23:48 Stephen Rothwell
2024-08-05 6:39 ` Satya Priya Kakitapalli (Temp)
2024-06-25 11:36 Mark Brown
2024-07-01 1:22 ` Stephen Rothwell
2023-12-03 23:30 Stephen Rothwell
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=20180426212330.GD25699@hector.attlocal.net \
--to=andy.gross@linaro.org \
--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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.