All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Alan Kao <nonerkao@gmail.com>
Cc: Palmer Dabbelt <palmer@sifive.com>, Albert Ou <albert@sifive.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Kamil Rytarowski <n54@gmx.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	patches@groups.riscv.org, linux-kernel@vger.kernel.org,
	Alan Kao <alankao@andestech.com>,
	Greentime Hu <greentime@andestech.com>
Subject: Re: [patches] [PATCH 1/6] riscv/ftrace: Add RECORD_MCOUNT support
Date: Wed, 10 Jan 2018 08:43:54 +0100	[thread overview]
Message-ID: <20180110074354.GA8800@lst.de> (raw)
In-Reply-To: <20180110073814.32338-2-alankao@andestech.com>

On Wed, Jan 10, 2018 at 03:38:09PM +0800, Alan Kao wrote:
> -LDFLAGS_vmlinux :=
> +ifeq ($(CONFIG_DYNAMIC_FTRACE),y)
> +	LDFLAGS_vmlinux := --no-relax
> +else
> +	LDFLAGS_vmlinux :=
> +endif

Why not:

LDFLAGS_vmlinux :=
ifeq ($(CONFIG_DYNAMIC_FTRACE),y)
LDFLAGS_vmlinux += --no-relax
endif

  reply	other threads:[~2018-01-10  7:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10  7:38 [PATCH 0/6] Add dynamic ftrace support for RISC-V platforms Alan Kao
2018-01-10  7:38 ` [PATCH 1/6] riscv/ftrace: Add RECORD_MCOUNT support Alan Kao
2018-01-10  7:43   ` Christoph Hellwig [this message]
2018-01-10  7:54     ` [patches] " Alan Kao
2018-01-10  7:38 ` [PATCH 2/6] riscv/ftrace: Add dynamic function tracer support Alan Kao
2018-01-10 16:32   ` Steven Rostedt
2018-01-10 16:36   ` Steven Rostedt
2018-01-11  8:02     ` Alan Kao
2018-01-10  7:38 ` [PATCH 3/6] riscv/ftrace: Add dynamic function graph " Alan Kao
2018-01-10  7:38 ` [PATCH 4/6] riscv/ftrace: Add ARCH_SUPPORTS_FTRACE_OPS support Alan Kao
2018-01-10  7:38 ` [PATCH 5/6] riscv/ftrace: Add DYNAMIC_FTRACE_WITH_REGS support Alan Kao
2018-01-10  7:38 ` [PATCH 6/6] riscv/ftrace: Add HAVE_FUNCTION_GRAPH_RET_ADDR_PTR support Alan Kao

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=20180110074354.GA8800@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=alankao@andestech.com \
    --cc=albert@sifive.com \
    --cc=greentime@andestech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=n54@gmx.com \
    --cc=nonerkao@gmail.com \
    --cc=palmer@sifive.com \
    --cc=patches@groups.riscv.org \
    --cc=rostedt@goodmis.org \
    --cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.