linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Torsten Duwe <duwe@lst.de>
To: Amit Daniel Kachhap <amit.kachhap@arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	julien.thierry@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Will Deacon <will.deacon@arm.com>,
	linux-kernel@vger.kernel.org, rostedt@goodmis.org,
	takahiro.akashi@linaro.org, mingo@redhat.com,
	jpoimboe@redhat.com, live-patching@vger.kernel.org,
	LAK <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5] arm64: implement ftrace with regs
Date: Sat, 15 Dec 2018 13:41:44 +0100	[thread overview]
Message-ID: <20181215134144.6b0cc45b@blackhole.lan> (raw)
In-Reply-To: <CADGdYn69reXed-DBMTCezNyNEgKn-h0NA-D6dnoRrJx2_bE71Q@mail.gmail.com>

On Fri, 14 Dec 2018 21:45:03 +0530
Amit Daniel Kachhap <amit.kachhap@arm.com> wrote:

> Sorry I didn't mention my environment. I am using 4.20-rc3 and it has
> all the above 8 extra patches
> mentioned by you.

So that should be fine.

> I read your change description in v3 patchset. You had mentioned there
> that graph caller
> is broken.

No, actually I thought I had fixed that for v4. Would you care to show
us an actual error message or some symptom?

	Torsten

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

  reply	other threads:[~2018-12-15 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 16:20 [PATCH v5] arm64: implement ftrace with regs Torsten Duwe
2018-12-13 17:31 ` Amit Daniel Kachhap
2018-12-14  9:47   ` Torsten Duwe
2018-12-14 16:15     ` Amit Daniel Kachhap
2018-12-15 12:41       ` Torsten Duwe [this message]
2018-12-17  4:22         ` Amit Daniel Kachhap
2018-12-17 13:34           ` Torsten Duwe
2019-01-04 14:13           ` Torsten Duwe

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=20181215134144.6b0cc45b@blackhole.lan \
    --to=duwe@lst.de \
    --cc=amit.kachhap@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=jpoimboe@redhat.com \
    --cc=julien.thierry@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=will.deacon@arm.com \
    /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).