From: Linus Walleij <linus.walleij@linaro.org>
To: Timur Tabi <timur@kernel.org>
Cc: Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
Lina Iyer <ilina@codeaurora.org>,
Stephen Boyd <swboyd@chromium.org>,
Mark Brown <broonie@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: next/master boot: 265 boots: 17 failed, 184 passed with 64 offline (next-20190730)
Date: Thu, 1 Aug 2019 10:09:42 +0200 [thread overview]
Message-ID: <CACRpkdbpBnO4KgpjYReafWKKoq0AX5kAb99tCC9LXE0_7sW7Jg@mail.gmail.com> (raw)
In-Reply-To: <c2e5cd69-2f95-fc47-4541-17a1d744f003@kernel.org>
On Thu, Aug 1, 2019 at 5:49 AM Timur Tabi <timur@kernel.org> wrote:
> On 7/31/19 12:58 PM, Jeffrey Hugo wrote:
> >>>
> >>> Timur/Stephen: any ideas?
> >
> > Timur's CAF account is no longer valid, I added his @kernel one.
>
> Delete everything specific to the QDF2400.
It appears Mark is still using it in his test farm, and now its sole
role is finding bugs in my code. Which it did! With so much elegance
that we could fix it up quickly.
> Qualcomm has made it very clear that they have no interest in developing
> ARM server chips. No QDF2400 system ever made it to official production.
That's sad. I remember we had lots of discussions around this at the
time. The ACPI code base and quirks we added is however used in
other Qualcomm-based machines now (what Lee is doing), so the effort
is not wasted at all.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-01 8:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d403574.1c69fb81.14163.65d3@mx.google.com>
2019-07-30 12:34 ` next/master boot: 265 boots: 17 failed, 184 passed with 64 offline (next-20190730) Mark Brown
2019-08-02 13:03 ` Neil Armstrong
2019-07-30 13:00 ` Mark Brown
2019-07-30 13:28 ` Mark Brown
2019-07-30 13:41 ` Mark Brown
2019-07-31 8:48 ` Linus Walleij
2019-07-31 10:39 ` Mark Brown
2019-08-05 9:23 ` Lee Jones
2019-07-31 15:13 ` Stephen Boyd
2019-07-31 17:58 ` Jeffrey Hugo
2019-08-01 3:49 ` Timur Tabi
2019-08-01 8:09 ` Linus Walleij [this message]
2019-08-01 16:17 ` Jeffrey Hugo
2019-08-02 2:51 ` Timur Tabi
2019-08-03 9:42 ` Linus Walleij
2019-08-12 14:07 ` Jeffrey Hugo
2019-08-14 9:05 ` Linus Walleij
2019-08-05 9:20 ` Lee Jones
2019-07-31 22:40 ` Linus Walleij
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=CACRpkdbpBnO4KgpjYReafWKKoq0AX5kAb99tCC9LXE0_7sW7Jg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=ilina@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=swboyd@chromium.org \
--cc=timur@kernel.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).