From: Jisheng Zhang <jszhang@kernel.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <anup.patel@wdc.com>,
Atish Patra <atishp@atishpatra.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kvm-riscv@lists.infradead.org
Subject: [PATCH 0/5] riscv: misc clean up
Date: Mon, 29 Nov 2021 00:07:36 +0800 [thread overview]
Message-ID: <20211128160741.2122-1-jszhang@kernel.org> (raw)
This series is a misc clean up: clean up useless LoCs, or make some
functions static, or mark function pointer as __initdata, or remove
one function().
Jisheng Zhang (5):
riscv: remove cpu_stop()
riscv: head: make secondary_start_common() static
riscv: kvm: make kvm_riscv_vcpu_fp_clean() static
riscv: errata: alternative: mark vendor_patch_func __initdata
riscv: head: remove useless __PAGE_ALIGNED_BSS and .balign
arch/riscv/errata/alternative.c | 3 ++-
arch/riscv/include/asm/smp.h | 2 --
arch/riscv/kernel/cpu-hotplug.c | 8 +-------
arch/riscv/kernel/head.S | 9 ++-------
arch/riscv/kvm/vcpu_fp.c | 2 +-
5 files changed, 6 insertions(+), 18 deletions(-)
--
2.34.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2021-11-28 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 16:07 Jisheng Zhang [this message]
2021-11-28 16:07 ` [PATCH 1/5] riscv: remove cpu_stop() Jisheng Zhang
2021-11-28 16:07 ` [PATCH 2/5] riscv: head: make secondary_start_common() static Jisheng Zhang
2021-11-28 16:07 ` [PATCH 3/5] riscv: kvm: make kvm_riscv_vcpu_fp_clean() static Jisheng Zhang
2021-12-03 13:23 ` Anup Patel
2021-11-28 16:07 ` [PATCH 4/5] riscv: errata: alternative: mark vendor_patch_func __initdata Jisheng Zhang
2021-11-28 16:07 ` [PATCH 5/5] riscv: head: remove useless __PAGE_ALIGNED_BSS and .balign Jisheng Zhang
2022-01-09 19:48 ` [PATCH 0/5] riscv: misc clean up Palmer Dabbelt
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=20211128160741.2122-1-jszhang@kernel.org \
--to=jszhang@kernel.org \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).