From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Bert Vermeulen <bert@biot.com>
Cc: Paul Burton <paulburton@kernel.org>,
"open list:MIPS GENERIC PLATFORM" <linux-mips@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arch: mips: Remove unused BOARD_INGENIC Kconfig option
Date: Mon, 28 Dec 2020 22:38:21 +0100 [thread overview]
Message-ID: <20201228213821.GA24617@alpha.franken.de> (raw)
In-Reply-To: <20201222203239.1489040-1-bert@biot.com>
On Tue, Dec 22, 2020 at 09:32:39PM +0100, Bert Vermeulen wrote:
> Board support depends on MACH_INGENIC, not BOARD_INGENIC.
you are missing the point here. BOARD_INGENIC is for enabling
Ingenic boards in a generic kernel, while MACH_INGENIC is for
building a Ingenic only kernel (usually for size/performance reasons).
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-12-28 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 20:32 [PATCH] arch: mips: Remove unused BOARD_INGENIC Kconfig option Bert Vermeulen
2020-12-28 21:38 ` 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=20201228213821.GA24617@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bert@biot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.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).