[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200809155312.D6D422075F@mail.kernel.org>
Date: Sun, 09 Aug 2020 15:53:12 +0000
From: Sasha Levin <sashal@...nel.org>
To: linux-kernel@...r.kernel.org
Cc: stable@...r.kernel.org
Subject: Re: [for-linus][PATCH 05/17] ftrace: Setup correct FTRACE_FL_REGS flags for module
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 8c4f3c3fa968 ("ftrace: Check module functions being traced on reload").
The bot has tested the following trees: v5.8, v5.7.13, v5.4.56, v4.19.137, v4.14.192, v4.9.232, v4.4.232.
v5.8: Build OK!
v5.7.13: Build OK!
v5.4.56: Build OK!
v4.19.137: Build OK!
v4.14.192: Build OK!
v4.9.232: Build OK!
v4.4.232: Failed to apply! Possible dependencies:
02a392a0439f ("ftrace: Add new type to distinguish what kind of ftrace_bug()")
97e9b4fca52b ("ftrace: Clean up ftrace_module_init() code")
b6b71f66a16a ("ftrace: Join functions ftrace_module_init() and ftrace_init_module()")
b7ffffbb46f2 ("ftrace: Add infrastructure for delayed enabling of module functions")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
Powered by blists - more mailing lists