From: Atish Patra <atish.patra@wdc.com>
To: linux-kernel@vger.kernel.org
Cc: Atish Patra <atish.patra@wdc.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <aghiti@upmem.com>,
Andrew Morton <akpm@linux-foundation.org>,
Anup Patel <anup@brainfault.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>,
linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Richard Fontana <rfontana@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [v1 PATCH 0/2] Cleanup isa string access and print
Date: Thu, 3 Oct 2019 18:19:58 -0700 [thread overview]
Message-ID: <20191004012000.2661-1-atish.patra@wdc.com> (raw)
This is a cleanup series addressing issues around isa string accesses
and prints. Patch 1 is actually a revised patch as a result of discussion
in the following thread.
http://lists.infradead.org/pipermail/linux-riscv/2019-September/006702.html
Patch 2 is an additional cleanup that tries to consolidate all isa
string related checks.
Atish Patra (2):
RISC-V: Remove unsupported isa string info print
RISC-V: Consolidate isa correctness check
arch/riscv/include/asm/processor.h | 1 +
arch/riscv/kernel/cpu.c | 85 ++++++++++++------------------
arch/riscv/kernel/cpufeature.c | 4 +-
arch/riscv/kernel/smpboot.c | 4 ++
4 files changed, 39 insertions(+), 55 deletions(-)
--
2.21.0
next reply other threads:[~2019-10-04 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 1:19 Atish Patra [this message]
2019-10-04 1:19 ` [v1 PATCH 1/2] RISC-V: Remove unsupported isa string info print Atish Patra
2019-10-08 15:39 ` Christoph Hellwig
2019-10-04 1:20 ` [v1 PATCH 2/2] RISC-V: Consolidate isa correctness check Atish Patra
2019-10-08 15:44 ` Christoph Hellwig
2019-10-09 22:02 ` Atish Patra
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=20191004012000.2661-1-atish.patra@wdc.com \
--to=atish.patra@wdc.com \
--cc=aghiti@upmem.com \
--cc=akpm@linux-foundation.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=rfontana@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®