public inbox for linux-mips@vger.kernel.org
 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,
	"Paul Burton" <paulburton@kernel.org>,
	"John Crispin" <john@phrozen.org>,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
	"Keguang Zhang" <keguang.zhang@gmail.com>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"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: Remove empty prom_free_prom_memory functions
Date: Thu, 7 Jan 2021 17:27:40 +0100	[thread overview]
Message-ID: <20210107162740.GE11882@alpha.franken.de> (raw)
In-Reply-To: <20210105213633.76912-1-tsbogend@alpha.franken.de>

On Tue, Jan 05, 2021 at 10:36:31PM +0100, Thomas Bogendoerfer wrote:
> Most of the prom_free_prom_memory functions are empty. With
> a new weak prom_free_prom_memory() we can remove all of them.
> 
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
>  arch/mips/alchemy/common/prom.c     | 4 ----
>  arch/mips/ar7/memory.c              | 5 -----
>  arch/mips/ath25/prom.c              | 4 ----
>  arch/mips/ath79/prom.c              | 5 -----
>  arch/mips/bcm47xx/prom.c            | 4 ----
>  arch/mips/bcm63xx/prom.c            | 4 ----
>  arch/mips/bmips/setup.c             | 4 ----
>  arch/mips/cobalt/setup.c            | 5 -----
>  arch/mips/fw/arc/memory.c           | 2 +-
>  arch/mips/fw/sni/sniprom.c          | 4 ----
>  arch/mips/generic/init.c            | 4 ----
>  arch/mips/lantiq/prom.c             | 4 ----
>  arch/mips/loongson2ef/common/init.c | 4 ----
>  arch/mips/loongson32/common/prom.c  | 4 ----
>  arch/mips/loongson64/init.c         | 4 ----
>  arch/mips/mm/init.c                 | 5 +++++
>  arch/mips/mti-malta/malta-memory.c  | 4 ----
>  arch/mips/netlogic/xlp/setup.c      | 5 -----
>  arch/mips/netlogic/xlr/setup.c      | 5 -----
>  arch/mips/pic32/pic32mzda/init.c    | 4 ----
>  arch/mips/pistachio/init.c          | 4 ----
>  arch/mips/ralink/prom.c             | 4 ----
>  arch/mips/rb532/prom.c              | 5 -----
>  arch/mips/sgi-ip27/ip27-memory.c    | 5 -----
>  arch/mips/sgi-ip32/ip32-memory.c    | 5 -----
>  arch/mips/sibyte/common/cfe.c       | 5 -----
>  arch/mips/txx9/generic/setup.c      | 4 ----
>  arch/mips/vr41xx/common/init.c      | 4 ----
>  28 files changed, 6 insertions(+), 114 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 ]

      parent reply	other threads:[~2021-01-07 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 21:36 [PATCH] MIPS: Remove empty prom_free_prom_memory functions Thomas Bogendoerfer
2021-01-05 22:38 ` Florian Fainelli
2021-01-07 16:27 ` 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=20210107162740.GE11882@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=chenhuacai@kernel.org \
    --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=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