From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/4] powerpc/vdso: No need to undef powerpc for 64-bit build
Date: Wed, 6 Dec 2023 10:18:19 -0600 [thread overview]
Message-ID: <20231206161819.GJ19790@gate.crashing.org> (raw)
In-Reply-To: <20231206115548.1466874-2-mpe@ellerman.id.au>
On Wed, Dec 06, 2023 at 10:55:46PM +1100, Michael Ellerman wrote:
> But the 64-bit compiler doesn't define powerpc in the first place,
Yes, only __powerpc__ (and __powerpc64__) :-)
Segher
next prev parent reply other threads:[~2023-12-06 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 11:55 [PATCH 1/4] powerpc/Makefile: Don't use $(ARCH) unnecessarily Michael Ellerman
2023-12-06 11:55 ` [PATCH 2/4] powerpc/vdso: No need to undef powerpc for 64-bit build Michael Ellerman
2023-12-06 16:18 ` Segher Boessenkool [this message]
2023-12-06 11:55 ` [PATCH 3/4] powerpc/Makefile: Default to ppc64le_defconfig when cross building Michael Ellerman
2023-12-06 11:55 ` [PATCH 4/4] powerpc/Makefile: Auto detect cross compiler Michael Ellerman
2023-12-06 16:25 ` Segher Boessenkool
2023-12-07 4:48 ` Michael Ellerman
2023-12-21 10:38 ` [PATCH 1/4] powerpc/Makefile: Don't use $(ARCH) unnecessarily Michael Ellerman
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=20231206161819.GJ19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).