All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Qing Zhang <zhangqing@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] MIPS: Loongson64: Remove unused sysconf members
Date: Fri, 12 Mar 2021 11:28:03 +0100	[thread overview]
Message-ID: <20210312102803.GD7027@alpha.franken.de> (raw)
In-Reply-To: <20210304110057.22144-2-zhangqing@loongson.cn>

On Thu, Mar 04, 2021 at 07:00:56PM +0800, Qing Zhang wrote:
> We don't need them anymore, They are uniform on all Loongson64 systems
> and have been fixed in DeviceTree.loongson3_platform_init is replaced
> with DTS + driver.
> 
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> Signed-off-by: Qing Zhang <zhangqing@loongson.cn>
> ---
>  .../include/asm/mach-loongson64/boot_param.h  |  9 ----
>  arch/mips/loongson64/Makefile                 |  2 +-
>  arch/mips/loongson64/env.c                    | 20 ---------
>  arch/mips/loongson64/platform.c               | 42 -------------------
>  4 files changed, 1 insertion(+), 72 deletions(-)
>  delete mode 100644 arch/mips/loongson64/platform.c

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-03-12 10:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 11:00 [PATCH 0/2] some cleanup code Qing Zhang
2021-03-04 11:00 ` [PATCH 1/2] MIPS: Loongson64: Remove unused sysconf members Qing Zhang
2021-03-05  2:32   ` Jiaxun Yang
2021-03-06  3:18     ` zhangqing
2021-03-12 10:28   ` Thomas Bogendoerfer [this message]
2021-03-04 11:00 ` [PATCH 2/2] MIPS: Loongson64: Move loongson_system_configuration to loongson.h Qing Zhang
2021-03-05  2:32   ` Jiaxun Yang
2021-03-05 10:01   ` Philippe Mathieu-Daudé
2021-03-06  3:12     ` zhangqing
2021-03-06  8:03   ` Thomas Bogendoerfer
2021-03-06  8:57     ` zhangqing
2021-03-09 10:42       ` Thomas Bogendoerfer
2021-03-06  9:00     ` Jiaxun Yang
2021-03-06  9:53       ` Thomas Bogendoerfer
2021-03-06 10:55         ` Jiaxun Yang
2021-03-08  9:49           ` Thomas Bogendoerfer
2021-03-09 14:48             ` Jiaxun Yang
2021-03-12 10:28   ` 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=20210312102803.GD7027@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=chenhuacai@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=zhangqing@loongson.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.