From: Mike Rapoport <rppt@linux.ibm.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: sboyd@kernel.org, opendmb@gmail.com,
Florian Fainelli <f.fainelli@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Allow either FLATMEM or SPARSEMEM on the multiplatform build
Date: Thu, 7 May 2020 13:09:11 +0300 [thread overview]
Message-ID: <20200507100911.GD683243@linux.ibm.com> (raw)
In-Reply-To: <20200507081409.GQ1551@shell.armlinux.org.uk>
Hi Russell,
On Thu, May 07, 2020 at 09:14:09AM +0100, Russell King - ARM Linux admin wrote:
> On Wed, May 06, 2020 at 04:50:07PM -0700, Florian Fainelli wrote:
> > Hi all,
> >
> > This patch series somehow got lost back in 2015, and while looking at
> > the various patches that we are carrying in our BRCMSTB downstream
> > kernel those two patches should have made it upstream.
>
> I don't believe it's a good idea for multiplatform.
>
> If you have a platform that relies on sparsemem within the multiplatform
> family, and you select flatmem, how would it boot?
>
> Sparsemem can support flatmem layouts, but flatmem can't support
> sparsemem layouts.
>
> So, allowing flatmem seems to go against the underlying principle of
> multiplatform support.
Currently neither of multiplafrom builds has SPARSEMEM enabled, so
unless I misread theses patches, they actually allow enabling SPARSEMEM
in menuconfig for custom builds based on a multiplatform config.
> --
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
--
Sincerely yours,
Mike.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-05-07 10:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 23:50 [PATCH 0/2] Allow either FLATMEM or SPARSEMEM on the multiplatform build Florian Fainelli
2020-05-06 23:50 ` [PATCH 1/2] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting Florian Fainelli
2020-05-07 7:27 ` Mike Rapoport
2020-05-07 10:30 ` Russell King - ARM Linux admin
2020-05-07 17:25 ` Florian Fainelli
2020-05-07 18:50 ` Russell King - ARM Linux admin
2020-05-07 19:38 ` Florian Fainelli
2020-05-07 20:08 ` [PATCH] arm: use SPARSMEM_STATIC when SPARSEMEM is enabled (Was: [PATCH 1/2] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting) Mike Rapoport
2020-05-08 20:20 ` Florian Fainelli
2020-05-07 20:29 ` [PATCH 1/2] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting Mike Rapoport
2020-05-07 20:47 ` Florian Fainelli
2020-05-08 21:41 ` Mike Rapoport
2020-05-08 21:45 ` Florian Fainelli
2020-05-06 23:50 ` [PATCH 2/2] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build Florian Fainelli
2020-05-07 7:27 ` Mike Rapoport
2020-05-07 20:11 ` Florian Fainelli
2020-05-18 15:58 ` Florian Fainelli
2020-05-18 19:45 ` Mike Rapoport
2020-05-19 7:59 ` Arnd Bergmann
2020-05-19 14:43 ` Mike Rapoport
2020-05-19 15:04 ` Russell King - ARM Linux admin
2020-05-19 15:27 ` Mike Rapoport
2020-05-19 15:32 ` Arnd Bergmann
2020-05-19 16:54 ` Russell King - ARM Linux admin
2020-05-19 17:59 ` Mike Rapoport
2020-05-19 20:42 ` Arnd Bergmann
2020-05-21 2:45 ` Florian Fainelli
2020-05-21 7:47 ` Arnd Bergmann
2020-05-07 8:14 ` [PATCH 0/2] " Russell King - ARM Linux admin
2020-05-07 10:09 ` Mike Rapoport [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=20200507100911.GD683243@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=opendmb@gmail.com \
--cc=sboyd@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).