stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: CKI Project <cki-project@redhat.com>
Cc: Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ❌ FAIL: Stable queue: queue-5.1
Date: Fri, 5 Jul 2019 10:57:35 -0400	[thread overview]
Message-ID: <20190705145735.GG10104@sasha-vm> (raw)
In-Reply-To: <cki.23B379E428.A2S9JGOBXU@redhat.com>

On Fri, Jul 05, 2019 at 10:12:51AM -0400, CKI Project 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: 8584aaf1c326 - Linux 5.1.16
>
>The results of these automated tests are provided below.
>
>    Overall result: FAILED (see details below)
>             Merge: FAILED
>
>
>
>
>When we attempted to merge the patchset, we received an error:
>
>  error: patch failed: arch/x86/kernel/ftrace.c:22
>  error: arch/x86/kernel/ftrace.c: patch does not apply
>  error: patch failed: kernel/trace/ftrace.c:34
>  error: kernel/trace/ftrace.c: patch does not apply
>  hint: Use 'git am --show-current-patch' to see the failed patch
>  Applying: ftrace/x86: Remove possible deadlock between register_kprobe() and ftrace_run_update_code()
>  Patch failed at 0001 ftrace/x86: Remove possible deadlock between register_kprobe() and ftrace_run_update_code()

That was me, should already be fixed.

--
Thanks,
Sasha

  reply	other threads:[~2019-07-05 14:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 14:12 ❌ FAIL: Stable queue: queue-5.1 CKI Project
2019-07-05 14:57 ` Sasha Levin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-08 19:00 CKI Project
2019-07-08 18:05 CKI Project
2019-07-08 18:23 ` Rachel Sibley
2019-07-09  4:41   ` ? " Murphy Zhou
2019-07-03 11:16  " CKI Project
2019-07-03 11:25 ` Greg KH
2019-07-03 12:01   ` Veronika Kabatova
2019-07-03 12:07     ` Greg KH
2019-07-03 12:32       ` Veronika Kabatova
2019-06-23 16:11  " CKI Project
2019-06-20  0:13 CKI Project
2019-06-20  5:34 ` Greg KH
2019-06-16 17:28 CKI Project
2019-06-16 14:22 CKI Project
2019-06-16  3:58 CKI Project
2019-06-15 19:12 CKI Project
2019-06-15 19:02 CKI Project
2019-06-15 16:38 CKI Project
2019-06-15 16:54 ` Greg KH
2019-06-15  9:57 CKI Project
2019-05-17 14:56 CKI Project
2019-05-17 15:01 ` Major Hayden
2019-05-14 17:18 CKI Project
2019-05-14 17:26 ` Greg KH
2019-05-14 17:39   ` Major Hayden
2019-05-09 12:47 CKI Project
2019-05-09 12:49 ` Major Hayden
2019-05-09 13:14   ` Greg KH
2019-05-09 13:24     ` 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=20190705145735.GG10104@sasha-vm \
    --to=sashal@kernel.org \
    --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).