From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
"Maciej W. Rozycki" <macro@linux-mips.org>,
"Paul Burton" <paulburton@kernel.org>,
"Paul Cercueil" <paul@crapouillou.net>,
"John Crispin" <john@phrozen.org>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Keguang Zhang" <keguang.zhang@gmail.com>,
"Huacai Chen" <chenhc@lemote.com>,
"James Hartley" <james.hartley@sondrel.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MIPS: Only include the platform file needed
Date: Wed, 13 May 2020 13:19:07 +0200 [thread overview]
Message-ID: <20200513111907.GB7151@alpha.franken.de> (raw)
In-Reply-To: <20200509230150.24466-1-tsbogend@alpha.franken.de>
On Sun, May 10, 2020 at 01:01:47AM +0200, Thomas Bogendoerfer wrote:
> Instead of including all Platform files, we simply include the
> needed one and avoid clashes with makefile variables.
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
> arch/mips/Kbuild.platforms | 73 +++++++++++++++++++++-------------------
> arch/mips/alchemy/Platform | 3 --
> arch/mips/ar7/Platform | 1 -
> arch/mips/ath25/Platform | 1 -
> arch/mips/ath79/Platform | 1 -
> arch/mips/bcm47xx/Platform | 1 -
> arch/mips/bcm63xx/Platform | 1 -
> arch/mips/bmips/Platform | 1 -
> arch/mips/cavium-octeon/Platform | 1 -
> arch/mips/cobalt/Platform | 1 -
> arch/mips/dec/Platform | 1 -
> arch/mips/generic/Platform | 1 -
> arch/mips/jazz/Platform | 1 -
> arch/mips/jz4740/Platform | 1 -
> arch/mips/lantiq/Platform | 1 -
> arch/mips/loongson2ef/Platform | 1 -
> arch/mips/loongson32/Platform | 1 -
> arch/mips/loongson64/Platform | 1 -
> arch/mips/mti-malta/Platform | 1 -
> arch/mips/netlogic/Platform | 1 -
> arch/mips/paravirt/Platform | 1 -
> arch/mips/pic32/Platform | 1 -
> arch/mips/pistachio/Platform | 1 -
> arch/mips/pnx833x/Platform | 1 -
> arch/mips/rb532/Platform | 1 -
> arch/mips/sgi-ip22/Platform | 2 --
> arch/mips/sgi-ip27/Platform | 3 --
> arch/mips/sgi-ip30/Platform | 3 --
> arch/mips/sgi-ip32/Platform | 1 -
> arch/mips/sibyte/Platform | 4 ---
> arch/mips/sni/Platform | 1 -
> arch/mips/txx9/Platform | 3 --
> 32 files changed, 39 insertions(+), 77 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-05-13 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 23:01 Thomas Bogendoerfer
2020-05-12 0:53 ` Joshua Kinard
2020-05-13 11:19 ` Thomas Bogendoerfer [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=20200513111907.GB7151@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chenhc@lemote.com \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=james.hartley@sondrel.com \
--cc=jiaxun.yang@flygoat.com \
--cc=john@phrozen.org \
--cc=keguang.zhang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=paul@crapouillou.net \
--cc=paulburton@kernel.org \
--cc=zajec5@gmail.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
all inboxes | Powered by JetHome®