From: Sedat Dilek <sedat.dilek@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Matthias Kaehlcke <mka@chromium.org>,
Dmitry Vyukov <dvyukov@google.com>,
Greg Hackmann <ghackmann@google.com>,
Luis Lozano <llozano@google.com>,
Michael Davidson <md@google.com>,
Paul Lawrence <paullawrence@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Ingo Molnar <mingo@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
llvmlinux@lists.linuxfoundation.org, sil2review@lists.osadl.org,
JBeulich@suse.com, Peter Zijlstra <peterz@infradead.org>,
Kees Cook <keescook@chromium.org>,
Colin Ian King <colin.king@canonical.com>
Subject: Re: [llvmlinux] clang fails on linux-next since commit 8bf705d13039
Date: Tue, 31 Jul 2018 13:07:43 +0200 [thread overview]
Message-ID: <CA+icZUVRsivw6yORyc=kiS0qYvno4PiR03uEx0LSmaDK3EmUEQ@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUXTKL+kO0HzdOfVgyECmW-QKawLipNBv-dh+BgXWURE=Q@mail.gmail.com>
On Tue, Jul 31, 2018 at 9:35 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> Looks good (beyond some ACPI errors).
>
> Fix pending in <linux-pm.git#acpi>...
>
> "ACPICA: AML Parser: ignore dispatcher error status during table load"
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=acpi&id=73c2a01c52b657f4a0ead6c95f64c5279efbd000
The real fix is...
"ACPICA: AML Parser: ignore control method status in module-level code"
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=460a53106ac39b74625d1104d9a113e0f3716c18
- sed@ -
next prev parent reply other threads:[~2018-07-31 11:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 9:09 Sedat Dilek
2018-07-30 9:19 ` Mark Rutland
2018-07-30 9:40 ` Sedat Dilek
2018-07-30 9:46 ` Mark Rutland
2018-07-30 12:28 ` Sedat Dilek
2018-07-30 12:57 ` Mark Rutland
2018-07-30 16:35 ` Nick Desaulniers
2018-07-30 16:40 ` Sedat Dilek
2018-07-31 7:04 ` Sedat Dilek
2018-07-31 7:35 ` Sedat Dilek
2018-07-31 11:07 ` Sedat Dilek [this message]
2018-07-31 7:24 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2018-03-17 11:13 Lukas Bulwahn
2018-03-19 6:43 ` Dmitry Vyukov
2018-03-19 17:29 ` Matthias Kaehlcke
[not found] ` <99fbbbe3-df05-446b-9ce0-55787ea038f3@googlegroups.com>
2018-05-06 10:44 ` Dmitry Vyukov
2018-05-06 10:48 ` Sedat Dilek
2018-05-07 7:34 ` Dmitry Vyukov
2018-05-28 16:05 ` [llvmlinux] " Sedat Dilek
2018-05-29 6:49 ` Jan Beulich
2018-06-01 13:14 ` Sedat Dilek
2018-07-29 18:12 ` Sedat Dilek
2018-07-30 8:21 ` Mark Rutland
2018-07-30 9:29 ` Sedat Dilek
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='CA+icZUVRsivw6yORyc=kiS0qYvno4PiR03uEx0LSmaDK3EmUEQ@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=JBeulich@suse.com \
--cc=colin.king@canonical.com \
--cc=dvyukov@google.com \
--cc=ghackmann@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=llozano@google.com \
--cc=llvmlinux@lists.linuxfoundation.org \
--cc=mark.rutland@arm.com \
--cc=md@google.com \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=ndesaulniers@google.com \
--cc=paullawrence@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=sil2review@lists.osadl.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