From: sashal@kernel.org (Sasha Levin)
To: linux-arm-kernel@lists.infradead.org
Subject: [for-next][PATCH 03/18] ARM: function_graph: Simplify with function_graph_entry()
Date: Fri, 23 Nov 2018 07:30:29 +0000 [thread overview]
Message-ID: <20181123073030.B07C0206B2@mail.kernel.org> (raw)
In-Reply-To: <20181122003331.771117906@goodmis.org>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 03274a3ffb44 tracing/fgraph: Adjust fgraph depth before calling trace return callback.
The bot has tested the following trees: v4.19.3, v4.14.82, v4.9.138, v4.4.164, v3.18.126.
v4.19.3: Build OK!
v4.14.82: Build OK!
v4.9.138: Build OK!
v4.4.164: Failed to apply! Possible dependencies:
Unable to calculate
v3.18.126: Failed to apply! Possible dependencies:
Unable to calculate
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-11-23 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181122002801.501220343@goodmis.org>
2018-11-22 0:28 ` [for-next][PATCH 03/18] ARM: function_graph: Simplify with function_graph_entry() Steven Rostedt
2018-11-23 7:30 ` Sasha Levin [this message]
2018-11-22 0:28 ` [for-next][PATCH 04/18] arm64: " Steven Rostedt
2018-11-27 18:07 ` Will Deacon
2018-11-27 18:26 ` Steven Rostedt
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=20181123073030.B07C0206B2@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).