linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tomislav Novak <tnovak@meta.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Will Deacon <will@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] ARM: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
Date: Fri, 23 Sep 2022 15:05:57 +0000	[thread overview]
Message-ID: <Yy3LUNer/ySqieyI@tnovak-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <CACRpkdZZFx3W3EHZh30FnQ+xH9ub_S7DZdGLJFQ_wBVN5EBVwA@mail.gmail.com>

On Thu, Sep 22, 2022 at 10:57:11AM +0200, Linus Walleij wrote:
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> 
> Can you put this patch into Russell's patch tracker please?

Thanks! Done: https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=9250/1

This bug came up while I was testing another patch[1] to make sure it doesn't
break stack unwinding in Thumb-2 builds.

[1] https://lore.kernel.org/r/20220921002446.3096120-1-tnovak@fb.com/

-- 
T.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-23 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 23:07 [PATCH] ARM: perf: Fix stacktraces for tracepoint events in THUMB2 kernels Tomislav Novak
2022-09-22  8:57 ` Linus Walleij
2022-09-23 15:05   ` Tomislav Novak [this message]
2022-10-03 21:56     ` Linus Walleij

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=Yy3LUNer/ySqieyI@tnovak-mbp.dhcp.thefacebook.com \
    --to=tnovak@meta.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=jolsa@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=will@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).