From: Atish Patra <atish.patra@wdc.com>
To: linux-kernel@vger.kernel.org
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Dmitriy Cherkasov <dmitriy@oss-tech.org>,
Anup Patel <anup@brainfault.org>,
Palmer Dabbelt <palmer@sifive.com>,
Johan Hovold <johan@kernel.org>,
Atish Patra <atish.patra@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Andreas Schwab <schwab@suse.de>,
linux-riscv@lists.infradead.org
Subject: [PATCH v2 0/4] Miscellaneous kernel command line fixes
Date: Wed, 10 Apr 2019 16:04:39 -0700 [thread overview]
Message-ID: <20190410230443.15729-1-atish.patra@wdc.com> (raw)
Assorted command line option fixes for RISC-V.
Changes from v1->v2.
1. Update pr_err string in patch (4/4) as per review.
Atish Patra (4):
RISC-V: Add RISC-V specific arch_match_cpu_phys_id
RISC-V: Fix of_get_cpu_node usage
RISC-V: Implement nosmp commandline option.
RISC-V: Support nr_cpus command line option.
arch/riscv/kernel/cpu.c | 3 +--
arch/riscv/kernel/smp.c | 5 +++++
arch/riscv/kernel/smpboot. | 0
arch/riscv/kernel/smpboot.c | 22 ++++++++++++++++++++--
4 files changed, 26 insertions(+), 4 deletions(-)
create mode 100644 arch/riscv/kernel/smpboot.
--
2.21.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-04-10 23:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 23:04 Atish Patra [this message]
2019-04-10 23:04 ` [PATCH v2 1/4] RISC-V: Add RISC-V specific arch_match_cpu_phys_id Atish Patra
2019-04-11 6:58 ` Christoph Hellwig
2019-04-10 23:04 ` [PATCH v2 2/4] RISC-V: Fix of_get_cpu_node usage Atish Patra
2019-04-11 6:59 ` Christoph Hellwig
2019-04-11 18:14 ` Atish Patra
2019-04-10 23:04 ` [PATCH v2 3/4] RISC-V: Implement nosmp commandline option Atish Patra
2019-04-11 7:01 ` Christoph Hellwig
2019-04-11 18:42 ` Atish Patra
2019-04-10 23:04 ` [PATCH v2 4/4] RISC-V: Support nr_cpus command line option 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=20190410230443.15729-1-atish.patra@wdc.com \
--to=atish.patra@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=dmitriy@oss-tech.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=schwab@suse.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;
as well as URLs for NNTP newsgroup(s).