linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
	"Keguang Zhang" <keguang.zhang@gmail.com>,
	"John Crispin" <john@phrozen.org>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] MIPS: replace add_memory_region with memblock
Date: Mon, 12 Oct 2020 12:31:23 +0200	[thread overview]
Message-ID: <20201012103123.GE7765@alpha.franken.de> (raw)
In-Reply-To: <20201009121449.64081-1-tsbogend@alpha.franken.de>

On Fri, Oct 09, 2020 at 02:14:46PM +0200, Thomas Bogendoerfer wrote:
> add_memory_region was the old interface for registering memory and
> was already changed to used memblock internaly. Replace it by
> directly calling memblock functions.
> 
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
> Changes in v3:
> 	removed early_init_dt_add_memory_arch and
> 	early_init_dt_reserve_memory_arch as there is nothing
> 	special about our version and we can use the generic ones
> 
> Changes in v2:
> 	fixed missing memblock include in fw/sni/sniprom.c
> 	tested on cobalt, IP22, IP28, IP30, IP32, JAZZ, SNI
> 
>  arch/mips/alchemy/common/prom.c               |  3 +-
>  arch/mips/ar7/memory.c                        |  2 +-
>  arch/mips/ath25/ar2315.c                      |  3 +-
>  arch/mips/ath25/ar5312.c                      |  3 +-
>  arch/mips/bcm47xx/prom.c                      |  3 +-
>  arch/mips/bcm47xx/setup.c                     |  2 +-
>  arch/mips/bcm63xx/setup.c                     |  2 +-
>  arch/mips/cavium-octeon/setup.c               | 24 ++++++-------
>  arch/mips/cobalt/setup.c                      |  3 +-
>  arch/mips/dec/prom/memory.c                   |  8 ++---
>  arch/mips/fw/arc/memory.c                     | 28 ++++++++++-----
>  arch/mips/fw/sni/sniprom.c                    |  4 +--
>  arch/mips/include/asm/bootinfo.h              |  7 ----
>  arch/mips/include/asm/netlogic/psb-bootinfo.h |  1 +
>  arch/mips/kernel/prom.c                       | 25 --------------
>  arch/mips/kernel/setup.c                      | 50 ++++-----------------------
>  arch/mips/loongson2ef/common/mem.c            | 12 ++-----
>  arch/mips/loongson32/common/prom.c            |  4 +--
>  arch/mips/netlogic/xlp/setup.c                |  2 +-
>  arch/mips/netlogic/xlr/setup.c                |  5 +--
>  arch/mips/ralink/of.c                         |  3 +-
>  arch/mips/rb532/prom.c                        |  2 +-
>  arch/mips/sgi-ip32/ip32-memory.c              |  3 +-
>  arch/mips/sibyte/common/cfe.c                 | 16 ++++-----
>  arch/mips/txx9/jmr3927/prom.c                 |  4 +--
>  arch/mips/txx9/rbtx4927/prom.c                |  5 +--
>  arch/mips/txx9/rbtx4938/prom.c                |  3 +-
>  arch/mips/txx9/rbtx4939/prom.c                |  4 +--
>  28 files changed, 82 insertions(+), 149 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 ]

  reply	other threads:[~2020-10-12 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 12:14 [PATCH v3] MIPS: replace add_memory_region with memblock Thomas Bogendoerfer
2020-10-12 10:31 ` Thomas Bogendoerfer [this message]
2020-10-14 12:47 ` Maciej W. Rozycki
2020-10-14 22:07   ` Thomas Bogendoerfer

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=20201012103123.GE7765@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=hauke@hauke-m.de \
    --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=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;
as well as URLs for NNTP newsgroup(s).