From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: liang wang <liang26812@gmail.com>
Cc: linux-kernel@vger.kernel.org, penberg@kernel.org,
geert@linux-m68k.org, rppt@kernel.org, akpm@linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] [RFC]ARM: ftrace: pause/unpause function graph tracer in cpu_suspend()
Date: Wed, 24 Feb 2021 10:39:44 +0000 [thread overview]
Message-ID: <20210224103944.GQ1463@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAG_0j0D9Vhc5F659ZrORLD4vh56MtGK8Zf4V1Ex3nXOjkLL1gg@mail.gmail.com>
On Wed, Feb 24, 2021 at 06:35:47PM +0800, liang wang wrote:
> Hi,all
>
> ftrace function_graph tracer always cause kernel panic on my ARM device with
> multiple CPUs, I found a solution for the problem on ARM64, refers to
> the patch above,
> I was wondering why this bugfix on ARM64 hasn't been upstreamed to ARM,
Patches get applied to the ARM tree after they've been submitted to
the patch system. If they don't get submitted to the patch system,
then they get buried and forgotten.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-24 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 5:35 [PATCH] ARM: ftrace: pause/unpause function graph tracer in cpu_suspend() Louis Wang
2021-02-24 10:35 ` [PATCH] [RFC]ARM: " liang wang
2021-02-24 10:39 ` Russell King - ARM Linux admin [this message]
2021-02-24 11:14 ` liang wang
2021-02-24 11:20 ` Russell King - ARM Linux admin
2021-02-24 11:36 ` liang wang
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=20210224103944.GQ1463@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=liang26812@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rppt@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).