From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: zhaoxiao <zhaoxiao@uniontech.com>
Cc: jiaxun.yang@flygoat.com, chenhuacai@kernel.org,
viro@zeniv.linux.org.uk, morbo@google.com, paul@crapouillou.net,
alobakin@pm.me, suxingxing@loongson.cn, tangyouling@loongson.cn,
yangtiezhu@loongson.cn, ralf@linux-mips.org, nathan@kernel.org,
masahiroy@kernel.org, keescook@chromium.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] MIPS: Makefile: Replace -pg with CC_FLAGS_FTRACE
Date: Wed, 21 Apr 2021 14:01:30 +0200 [thread overview]
Message-ID: <20210421120130.GB8637@alpha.franken.de> (raw)
In-Reply-To: <20210420070052.25593-1-zhaoxiao@uniontech.com>
On Tue, Apr 20, 2021 at 03:00:52PM +0800, zhaoxiao wrote:
> This patch replaces the "open-coded" -pg compile flag with a CC_FLAGS_FTRACE
> makefile variable which architectures can override if a different option
> should be used for code generation.
>
> Signed-off-by: zhaoxiao <zhaoxiao@uniontech.com>
> ---
> v3:Modify the description for the patch.
> arch/mips/boot/compressed/Makefile | 2 +-
> arch/mips/kernel/Makefile | 8 ++++----
> arch/mips/vdso/Makefile | 4 ++--
> 3 files changed, 7 insertions(+), 7 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-04-21 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 7:00 [PATCH v3] MIPS: Makefile: Replace -pg with CC_FLAGS_FTRACE zhaoxiao
2021-04-21 12:01 ` Thomas Bogendoerfer [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=20210421120130.GB8637@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alobakin@pm.me \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=paul@crapouillou.net \
--cc=ralf@linux-mips.org \
--cc=suxingxing@loongson.cn \
--cc=tangyouling@loongson.cn \
--cc=viro@zeniv.linux.org.uk \
--cc=yangtiezhu@loongson.cn \
--cc=zhaoxiao@uniontech.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).