From: Greg KH <greg@kroah.com>
To: CKI <cki-project@redhat.com>
Cc: Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: Stable queue: queue-4.20
Date: Mon, 14 Jan 2019 17:22:14 +0100 [thread overview]
Message-ID: <20190114162213.GA7933@kroah.com> (raw)
In-Reply-To: <cki.D166115C6C4BFBC98FE278ED55A54F19F927C705BDD3185278D866AE5CB0EB0A.7FJ5L7A1OYXG9W423D4IIQG6SM1W8NHPVYBBTCL6@redhat.com>
On Mon, Jan 14, 2019 at 10:16:00AM -0500, CKI wrote:
> Hello,
>
> We ran automated tests on a patchset that was proposed for merging into this
> kernel tree. The patches were applied to:
>
> Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> Commit: 8aab2b4410a2 Linux 4.20.2
>
> The results of these automated tests are provided below.
>
> Overall result: FAILED (see details below)
> Patch merge: OK
> Compile: FAILED
>
> We attempted to compile the kernel for multiple architectures, but the compile
> failed on one or more architectures:
>
> s390x: FAILED (build log attached: build_s390.log.gz)
> powerpc64le: FAILED (build log attached: build_powerpc.log.gz)
> aarch64: FAILED (build log attached: build_arm64.log.gz)
> x86_64: FAILED (build log attached: build_x86_64.log.gz)
Known failure, should be fixed soon, sorry for the noise...
greg k-h
next prev parent reply other threads:[~2019-01-14 16:22 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 15:16 Stable queue: queue-4.20 CKI
2019-01-14 16:22 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-07 21:21 CKI
2019-03-03 23:14 CKI
2019-03-03 13:27 CKI
2019-03-03 6:10 CKI
2019-02-28 22:21 CKI
2019-02-27 12:19 CKI
2019-02-27 1:09 CKI
2019-02-26 13:33 CKI
2019-02-26 8:09 CKI
2019-02-26 7:10 CKI
2019-02-26 5:58 CKI
2019-02-25 1:19 CKI
2019-02-24 23:15 CKI
2019-02-18 19:49 CKI
2019-02-18 17:40 CKI
2019-02-18 10:50 CKI
2019-02-18 7:45 CKI
2019-02-15 23:42 CKI
2019-02-12 12:38 CKI
2019-02-11 21:27 CKI
2019-02-11 21:26 CKI
2019-02-11 18:42 CKI
2019-02-11 17:58 CKI
2019-02-10 17:20 CKI
2019-02-10 16:54 CKI
2019-02-10 15:40 CKI
2019-02-09 23:20 CKI
2019-02-04 11:34 CKI
2019-02-04 6:26 CKI
2019-02-04 7:24 ` Greg KH
2019-02-06 9:51 ` Nikolai Kondrashov
2019-02-02 19:20 CKI
2019-02-02 12:55 CKI
2019-01-31 22:12 CKI
2019-01-30 8:03 CKI
2019-01-30 8:16 ` Greg KH
2019-01-30 9:10 ` Major Hayden
2019-01-28 21:36 CKI
2019-01-29 7:41 ` Nikolai Kondrashov
2019-01-29 7:48 ` Nikolai Kondrashov
2019-01-28 21:36 CKI
2019-01-28 13:37 CKI
2019-01-27 22:47 CKI
2019-01-27 22:30 CKI
2019-01-26 21:50 CKI
2019-01-26 11:39 CKI
2019-01-25 14:32 CKI
2019-01-25 0:39 CKI
2019-01-24 22:37 CKI
2019-01-23 21:09 CKI
2019-01-21 23:18 CKI
2019-01-21 18:10 CKI
2019-01-21 14:22 CKI
2019-01-21 15:35 ` Major Hayden
2019-01-18 23:36 CKI
2019-01-18 6:09 CKI
2019-01-11 10:54 CKI
2019-01-11 3:16 CKI
2019-01-10 22:04 CKI
2019-01-10 20:51 CKI
2019-01-10 18:52 CKI
2019-01-10 16:43 CKI
2019-01-08 22:31 CKI
2019-01-09 14:39 ` Greg KH
2019-01-09 14:48 ` Major Hayden
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=20190114162213.GA7933@kroah.com \
--to=greg@kroah.com \
--cc=cki-project@redhat.com \
--cc=stable@vger.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).