From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 1/4] powerpc/Makefile: Don't use $(ARCH) unnecessarily
Date: Thu, 21 Dec 2023 21:38:20 +1100 [thread overview]
Message-ID: <170315510011.2192823.10396130939206059927.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20231206115548.1466874-1-mpe@ellerman.id.au>
On Wed, 06 Dec 2023 22:55:45 +1100, Michael Ellerman wrote:
> There's no need to use $(ARCH) for references to the arch directory in
> the source tree, it is always arch/powerpc.
>
>
Applied to powerpc/next.
[1/4] powerpc/Makefile: Don't use $(ARCH) unnecessarily
https://git.kernel.org/powerpc/c/dc420877b5bd92db5d80df6b117c7a0f987290af
[2/4] powerpc/vdso: No need to undef powerpc for 64-bit build
https://git.kernel.org/powerpc/c/42449052c94f22e18e01d71147d8fd75cb58132a
[3/4] powerpc/Makefile: Default to ppc64le_defconfig when cross building
https://git.kernel.org/powerpc/c/22f17b02f88b48c01d3ac38d40d2b0b695ab2d10
[4/4] powerpc/Makefile: Auto detect cross compiler
https://git.kernel.org/powerpc/c/402928b58ec62b42b11992a7b51ff2f56ed65a18
cheers
prev parent reply other threads:[~2023-12-21 10:45 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
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 ` 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=170315510011.2192823.10396130939206059927.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--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).