From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, atishp@atishpatra.org, heiko@sntech.de,
arnd@arndb.de, anup@brainfault.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] Add PMEM support for RISC-V
Date: Fri, 09 Dec 2022 01:30:18 +0000 [thread overview]
Message-ID: <167054941883.3046.11002142340745112697.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221114090536.1662624-1-apatel@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 14 Nov 2022 14:35:33 +0530 you wrote:
> The Linux NVDIMM PEM drivers require arch support to map and access the
> persistent memory device. This series adds RISC-V PMEM support using
> recently added Svpbmt and Zicbom support.
>
> First two patches are fixes and remaining two patches add the required
> PMEM support for Linux RISC-V.
>
> [...]
Here is the summary with links:
- [v6,1/3] RISC-V: Fix MEMREMAP_WB for systems with Svpbmt
https://git.kernel.org/riscv/c/b91676fc16cd
- [v6,2/3] RISC-V: Implement arch specific PMEM APIs
https://git.kernel.org/riscv/c/a49ab905a1fc
- [v6,3/3] RISC-V: Enable PMEM drivers
https://git.kernel.org/riscv/c/497bcbe3ce04
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, atishp@atishpatra.org, heiko@sntech.de,
arnd@arndb.de, anup@brainfault.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] Add PMEM support for RISC-V
Date: Fri, 09 Dec 2022 01:30:18 +0000 [thread overview]
Message-ID: <167054941883.3046.11002142340745112697.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221114090536.1662624-1-apatel@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 14 Nov 2022 14:35:33 +0530 you wrote:
> The Linux NVDIMM PEM drivers require arch support to map and access the
> persistent memory device. This series adds RISC-V PMEM support using
> recently added Svpbmt and Zicbom support.
>
> First two patches are fixes and remaining two patches add the required
> PMEM support for Linux RISC-V.
>
> [...]
Here is the summary with links:
- [v6,1/3] RISC-V: Fix MEMREMAP_WB for systems with Svpbmt
https://git.kernel.org/riscv/c/b91676fc16cd
- [v6,2/3] RISC-V: Implement arch specific PMEM APIs
https://git.kernel.org/riscv/c/a49ab905a1fc
- [v6,3/3] RISC-V: Enable PMEM drivers
https://git.kernel.org/riscv/c/497bcbe3ce04
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-12-09 1:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 9:05 [PATCH v6 0/3] Add PMEM support for RISC-V Anup Patel
2022-11-14 9:05 ` Anup Patel
2022-11-14 9:05 ` [PATCH v6 1/3] RISC-V: Fix MEMREMAP_WB for systems with Svpbmt Anup Patel
2022-11-14 9:05 ` Anup Patel
2022-11-14 9:05 ` [PATCH v6 2/3] RISC-V: Implement arch specific PMEM APIs Anup Patel
2022-11-14 9:05 ` Anup Patel
2022-11-14 9:05 ` [PATCH v6 3/3] RISC-V: Enable PMEM drivers Anup Patel
2022-11-14 9:05 ` Anup Patel
2022-11-14 16:41 ` [PATCH v6 0/3] Add PMEM support for RISC-V Conor Dooley
2022-11-14 16:41 ` Conor Dooley
2022-11-19 12:41 ` Anup Patel
2022-11-19 12:41 ` Anup Patel
2022-11-19 12:59 ` Conor Dooley
2022-11-19 12:59 ` Conor Dooley
2022-12-03 6:12 ` Anup Patel
2022-12-03 6:12 ` Anup Patel
2022-12-08 23:47 ` Palmer Dabbelt
2022-12-08 23:47 ` Palmer Dabbelt
2022-12-09 1:30 ` patchwork-bot+linux-riscv [this message]
2022-12-09 1:30 ` patchwork-bot+linux-riscv
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=167054941883.3046.11002142340745112697.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=arnd@arndb.de \
--cc=atishp@atishpatra.org \
--cc=heiko@sntech.de \
--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 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.