From: James Hogan <jhogan@kernel.org>
To: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: Always use -march=<arch>, not -<arch> shortcuts
Date: Wed, 20 Jun 2018 22:30:32 +0100 [thread overview]
Message-ID: <20180620213031.GB22606@jamesdev> (raw)
In-Reply-To: <20180619003800.32129-1-paul.burton@mips.com>
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
On Mon, Jun 18, 2018 at 05:37:59PM -0700, Paul Burton wrote:
> Resolve this problem by using the long-form -march=<arch> in all cases,
> which makes it through the arch/mips/vdso/Makefile's filtering & is thus
> consistently used to build both the kernel proper & the VDSO.
Reviewed-by: James Hogan <jhogan@kernel.org>
Cheers
James
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2018-06-20 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 0:37 [PATCH] MIPS: Always use -march=<arch>, not -<arch> shortcuts Paul Burton
2018-06-20 21:30 ` James Hogan [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=20180620213031.GB22606@jamesdev \
--to=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=stable@vger.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).