stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: "tip-bot2 for Borislav Petkov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Sergei Trofimovich <slyfox@gentoo.org>
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [tip: x86/urgent] x86: Fix early boot crash on gcc-10, third try
Date: Tue, 19 May 2020 11:49:06 +0000	[thread overview]
Message-ID: <20200519114908.1574B20709@mail.kernel.org> (raw)
In-Reply-To: <158954160454.17951.15828011095215471629.tip-bot2@tip-bot2>

Hi

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.6.13, v5.4.41, v4.19.123, v4.14.180, v4.9.223, v4.4.223.

v5.6.13: Build OK!
v5.4.41: Build OK!
v4.19.123: Failed to apply! Possible dependencies:
    53c99bd665a2 ("init: add arch_call_rest_init to allow stack switching")
    ec0bbef66f86 ("Compiler Attributes: homogenize __must_be_array")

v4.14.180: Failed to apply! Possible dependencies:
    53c99bd665a2 ("init: add arch_call_rest_init to allow stack switching")
    771c035372a0 ("deprecate the '__deprecated' attribute warnings entirely and for good")
    815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h mutually exclusive")
    8793bb7f4a9d ("kbuild: add macro for controlling warnings to linux/compiler.h")
    cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
    ec0bbef66f86 ("Compiler Attributes: homogenize __must_be_array")

v4.9.223: Failed to apply! Possible dependencies:
    1cec20f0ea0e ("dma-buf: Restart reservation_object_wait_timeout_rcu() after writes")
    38b8d208a454 ("sched/headers: Prepare for new header dependencies before moving code to <linux/sched/nmi.h>")
    555570d744f8 ("sched/clock: Update static_key usage")
    78010cd9736e ("dma-buf/fence: add an lockdep_assert_held()")
    83b96794e0ea ("x86/xen: split off smp_pv.c")
    983de5f97169 ("firmware: tegra: Add BPMP support")
    9881b024b7d7 ("sched/clock: Delay switching sched_clock to stable")
    a52482d9355e ("x86/xen: split off smp_hvm.c")
    aa1c84e8ca7f ("x86/xen: split xen_cpu_die()")
    acb04058de49 ("sched/clock: Fix hotplug crash")
    b52992c06c90 ("drm/i915: Support asynchronous waits on struct fence from i915_gem_request")
    ca791d7f4256 ("firmware: tegra: Add IVC library")
    e601757102cf ("sched/headers: Prepare for new header dependencies before moving code to <linux/sched/clock.h>")
    f54d1867005c ("dma-buf: Rename struct fence to dma_fence")
    fedf54132d24 ("dma-buf: Restart reservation_object_get_fences_rcu() after writes")

v4.4.223: Failed to apply! Possible dependencies:
    090e77c391dd ("cpu/hotplug: Restructure FROZEN state handling")
    1cf4f629d9d2 ("cpu/hotplug: Move online calls to hotplugged cpu")
    4baa0afc6719 ("cpu/hotplug: Convert the hotplugged cpu work to a state machine")
    949338e35131 ("cpu/hotplug: Move scheduler cpu_online notifier to hotplug core")
    984581728eb4 ("cpu/hotplug: Split out cpu down functions")
    ba997462435f ("cpu/hotplug: Restructure cpu_up code")
    cff7d378d3fd ("cpu/hotplug: Convert to a state machine for the control processor")
    fc6d73d67436 ("arch/hotplug: Call into idle with a proper state")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha

      reply	other threads:[~2020-05-19 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200314164451.346497-1-slyfox@gentoo.org>
2020-05-15 11:20 ` [tip: x86/urgent] x86: Fix early boot crash on gcc-10, third try tip-bot2 for Borislav Petkov
2020-05-19 11:49   ` Sasha Levin [this message]

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=20200519114908.1574B20709@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=slyfox@gentoo.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).