From: Nicholas Piggin <npiggin@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: remove leftover code of old GCC version checks
Date: Tue, 2 Oct 2018 09:51:21 +1000 [thread overview]
Message-ID: <20181002095121.3f0326f7@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <1538374224-3742-1-git-send-email-yamada.masahiro@socionext.com>
On Mon, 1 Oct 2018 15:10:24 +0900
Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> Clean up the leftover of commit f2910f0e6835 ("powerpc: remove old
> GCC version checks").
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> My patch had been sent earlier, with more clean-ups:
> https://lore.kernel.org/patchwork/patch/977805/
Sorry, I missed or forgot about your patch :(
Thanks for tidying up my mess!
Acked-by: Nicholas Piggin <npiggin@gmail.com>
>
> Anyway, this cleans up the left-over of the Nicholas' one.
>
>
> arch/powerpc/Makefile | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
> index 2ecd0976..b094375 100644
> --- a/arch/powerpc/Makefile
> +++ b/arch/powerpc/Makefile
> @@ -400,10 +400,6 @@ archclean:
>
> archprepare: checkbin
>
> -# Use the file '.tmp_gas_check' for binutils tests, as gas won't output
> -# to stdout and these checks are run even on install targets.
> -TOUT := .tmp_gas_check
> -
> # Check toolchain versions:
> # - gcc-4.6 is the minimum kernel-wide version so nothing required.
> checkbin:
> @@ -414,7 +410,3 @@ checkbin:
> echo -n '*** Please use a different binutils version.' ; \
> false ; \
> fi
> -
> -
> -CLEAN_FILES += $(TOUT)
> -
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-10-01 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 6:10 [PATCH] powerpc: remove leftover code of old GCC version checks Masahiro Yamada
2018-10-01 23:51 ` Nicholas Piggin [this message]
2018-10-11 8:35 ` 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=20181002095121.3f0326f7@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=yamada.masahiro@socionext.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).