From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kvm-ppc@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 0/3] powerpc: some header search path cleanups
Date: Fri, 18 Jan 2019 11:50:04 +0900 [thread overview]
Message-ID: <CAK7LNATkYYaZ68dmYACfadp+sPVbxWJ3r2KdX-7wJdzaCsKD+A@mail.gmail.com> (raw)
In-Reply-To: <1547176954-17739-1-git-send-email-yamada.masahiro@socionext.com>
Hi Michael,
On Fri, Jan 11, 2019 at 2:20 PM Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
>
> I am trying to get rid of crappy magic from Kbuild core makefiles.
>
> Before that, I want to drop as many useless paths as possible.
> Actually, many Makefiles are adding around pointless options.
>
> This series cleans some powerpc Makefiles.
> (only compile-tested by 0day bot)
Could you apply this series to ppc tree if you are fine with it?
> Masahiro Yamada (3):
> KVM: powerpc: remove -I. header search paths
> powerpc: remove redundant header search path additions
> powerpc: math-emu: remove unneeded header search paths
>
> arch/powerpc/Makefile | 4 ++--
> arch/powerpc/kvm/Makefile | 5 -----
> arch/powerpc/math-emu/Makefile | 2 +-
> 3 files changed, 3 insertions(+), 8 deletions(-)
>
> --
> 2.7.4
>
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2019-01-18 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 3:22 [PATCH 0/3] powerpc: some header search path cleanups Masahiro Yamada
2019-01-11 3:22 ` [PATCH 1/3] KVM: powerpc: remove -I. header search paths Masahiro Yamada
2019-01-24 3:40 ` [1/3] " Michael Ellerman
2019-01-11 3:22 ` [PATCH 2/3] powerpc: remove redundant header search path additions Masahiro Yamada
2019-01-11 3:22 ` [PATCH 3/3] powerpc: math-emu: remove unneeded header search paths Masahiro Yamada
2019-01-18 2:50 ` Masahiro Yamada [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=CAK7LNATkYYaZ68dmYACfadp+sPVbxWJ3r2KdX-7wJdzaCsKD+A@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).