From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [PATCH v2 0/3] RISC-V: Add new smp features
Date: Thu, 30 Aug 2018 07:11:20 -0700 [thread overview]
Message-ID: <20180830141120.GA1724@infradead.org> (raw)
In-Reply-To: <CAAhSdy0=ROMqkbgqcKLSdM11TBOeD65GR42s0j_HOYd+y-=jmg@mail.gmail.com>
On Thu, Aug 30, 2018 at 09:53:50AM -0400, Anup Patel wrote:
> > Atish Patra (3):
> > RISC-V: Add logical CPU indexing for RISC-V
> > RISC-V: Use Linux logical cpu number instead of hartid
> > RISC-V: Support cpu hotplug.
> >
>
> This series looks good to me.
Hmm, that series didn't make it to my inbox, neither directly, nor
through the linux-riscv list. Where did you see it?
next prev parent reply other threads:[~2018-08-30 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1535445370-19004-1-git-send-email-atish.patra@wdc.com>
2018-08-30 13:53 ` [PATCH v2 0/3] RISC-V: Add new smp features Anup Patel
2018-08-30 14:11 ` Christoph Hellwig [this message]
2018-08-30 14:15 ` Anup Patel
2018-08-30 14:18 ` Anup Patel
2018-08-30 16:04 ` Atish Patra
[not found] ` <1535445370-19004-2-git-send-email-atish.patra@wdc.com>
2018-08-31 6:03 ` [PATCH v2 1/3] RISC-V: Add logical CPU indexing for RISC-V Christoph Hellwig
2018-09-04 17:59 ` Atish Patra
[not found] ` <1535445370-19004-3-git-send-email-atish.patra@wdc.com>
2018-08-31 6:11 ` [PATCH v2 2/3] RISC-V: Use Linux logical cpu number instead of hartid Christoph Hellwig
2018-09-04 20:35 ` Atish Patra
2018-09-04 21:36 ` Christoph Hellwig
2018-09-04 21:43 ` Atish Patra
2018-09-05 19:03 ` Christoph Hellwig
[not found] ` <1535445370-19004-4-git-send-email-atish.patra@wdc.com>
2018-08-31 6:18 ` [PATCH v2 3/3] RISC-V: Support cpu hotplug Christoph Hellwig
2018-09-04 18:08 ` Atish Patra
2018-09-04 21:36 ` Christoph Hellwig
2018-09-04 21:40 ` 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=20180830141120.GA1724@infradead.org \
--to=hch@infradead.org \
--cc=linux-riscv@lists.infradead.org \
/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).