Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	rostedt@goodmis.org
Subject: Re: [PATCH] ftrace: arm64: remove static ftrace
Date: Fri, 25 Nov 2022 13:24:50 +0000	[thread overview]
Message-ID: <166937831148.3465406.15947472486766807556.b4-ty@kernel.org> (raw)
In-Reply-To: <20221122163624.1225912-1-mark.rutland@arm.com>

On Tue, 22 Nov 2022 16:36:24 +0000, Mark Rutland wrote:
> The build test robot pointer out that there's a build failure when:
> 
>   CONFIG_HAVE_DYNAMIC_FTRACE_WITH_ARGS=y
>   CONFIG_DYNAMIC_FTRACE_WITH_ARGS=n
> 
> ... due to some mismatched ifdeffery, some of which checks
> CONFIG_HAVE_DYNAMIC_FTRACE_WITH_ARGS, and some of which checks
> CONFIG_DYNAMIC_FTRACE_WITH_ARGS, leading to some missing definitions expected
> by the core code when CONFIG_DYNAMIC_FTRACE=n and consequently
> CONFIG_DYNAMIC_FTRACE_WITH_ARGS=n.
> 
> [...]

Applied to arm64 (for-next/ftrace), thanks!

[1/1] ftrace: arm64: remove static ftrace
      https://git.kernel.org/arm64/c/cfce092dae95

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

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

      parent reply	other threads:[~2022-11-25 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 16:36 [PATCH] ftrace: arm64: remove static ftrace Mark Rutland
2022-11-22 17:04 ` Steven Rostedt
2022-11-25 13:24 ` Will Deacon [this message]

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=166937831148.3465406.15947472486766807556.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=rostedt@goodmis.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