All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: alankao@andestech.com, linux-riscv@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv/ftrace: Fix the problem modules cannot find _mcount
Date: Mon,  4 Jun 2018 13:30:27 -0700	[thread overview]
Message-ID: <20180604203028.13886-1-palmer@sifive.com> (raw)
In-Reply-To: <1525749717-384-1-git-send-email-alankao@andestech.com>

I've rewritten the commit message to match what this patch actually
does.  Assuming it's OK, I'll include it as part of the commits for this
merge window.

Thanks!

WARNING: multiple messages have this Message-ID (diff)
From: palmer@sifive.com (Palmer Dabbelt)
To: linux-riscv@lists.infradead.org
Subject: [PATCH] riscv/ftrace: Fix the problem modules cannot find _mcount
Date: Mon,  4 Jun 2018 13:30:27 -0700	[thread overview]
Message-ID: <20180604203028.13886-1-palmer@sifive.com> (raw)
In-Reply-To: <1525749717-384-1-git-send-email-alankao@andestech.com>

I've rewritten the commit message to match what this patch actually
does.  Assuming it's OK, I'll include it as part of the commits for this
merge window.

Thanks!

  parent reply	other threads:[~2018-06-04 20:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08  3:21 [PATCH] riscv/ftrace: Fix the problem modules cannot find _mcount Alan Kao
2018-05-08  3:21 ` Alan Kao
2018-05-08 13:11 ` Steven Rostedt
2018-05-08 13:11   ` Steven Rostedt
2018-05-09  2:36   ` Alan Kao
2018-05-09  2:36     ` Alan Kao
2018-05-09  3:02     ` Steven Rostedt
2018-05-09  3:02       ` Steven Rostedt
2018-06-04 20:30 ` Palmer Dabbelt [this message]
2018-06-04 20:30   ` Palmer Dabbelt
2018-06-04 20:30   ` [PATCH] riscv/ftrace: Export _mcount when FUNCTION_GRAPH_TRACER isn't set Palmer Dabbelt
2018-06-04 20:30     ` Palmer Dabbelt
2018-06-05  1:12     ` Alan Kao
2018-06-05  1:12       ` 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=20180604203028.13886-1-palmer@sifive.com \
    --to=palmer@sifive.com \
    --cc=alankao@andestech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.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 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.