linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	list@opendingux.net, Kees Cook <keescook@chromium.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] MIPS: Avoid macro redefinitions
Date: Wed, 21 Jul 2021 18:17:19 +0200	[thread overview]
Message-ID: <20210721161719.GA9805@alpha.franken.de> (raw)
In-Reply-To: <7YIIWQ.1TU3IBLL4KNC2@crapouillou.net>

On Mon, Jul 19, 2021 at 11:10:55PM +0100, Paul Cercueil wrote:
> > >   #ifndef TOOLCHAIN_SUPPORTS_VIRT
> > 
> > Same question for GAS version support for virt?
> > Documentation/process/changes.rst
> > says GNU binutils 2.23+ is required for building the kernel.
> > If we still need to support, have you tested this change on such an
> > older version of GNU binutils?
> 
> I have no idea about virt support - I hope Thomas can answer this.

virt support was added in 2.24 and xpa in 2.25. So we still need the
TOOLCHAIN defines for it.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  parent reply	other threads:[~2021-07-21 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 13:07 [PATCH] MIPS: Avoid macro redefinitions Paul Cercueil
2021-07-19 21:43 ` Nick Desaulniers
2021-07-19 22:10   ` Paul Cercueil
2021-07-19 22:23     ` Nick Desaulniers
2021-07-21 16:17     ` Thomas Bogendoerfer [this message]
2021-07-27 20:25       ` Nick Desaulniers

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=20210721161719.GA9805@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=clang-built-linux@googlegroups.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=list@opendingux.net \
    --cc=ndesaulniers@google.com \
    --cc=paul@crapouillou.net \
    /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).