From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Joe Lawrence <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org, x86@kernel.org,
linuxppc-dev@lists.ozlabs.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Subject: Re: powerpc: remote save_stack_trace_tsk_reliable export
Date: Mon, 4 Mar 2019 11:48:08 +1100 (AEDT) [thread overview]
Message-ID: <44CLwm707Rz9sNF@ozlabs.org> (raw)
In-Reply-To: <20190301191721.4010-1-joe.lawrence@redhat.com>
On Fri, 2019-03-01 at 19:17:21 UTC, Joe Lawrence wrote:
> As tglx points out, there are no in-tree module users of
> save_stack_trace_tsk_reliable() and its x86 counterpart is not exported,
> so remove the powerpc symbol export.
>
> Suggested-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
> Acked-by: Balbir Singh <bsingharora@gmail.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/39070a96a1c2c502b2f77972ba8c2eba
cheers
prev parent reply other threads:[~2019-03-04 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 19:17 [PATCH] powerpc: remote save_stack_trace_tsk_reliable export Joe Lawrence
2019-03-03 20:05 ` Singh, Balbir
2019-03-04 0:48 ` Michael Ellerman [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=44CLwm707Rz9sNF@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=joe.lawrence@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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).