All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	conor.dooley@microchip.com, evan@rivosinc.com,
	andy.chiu@sifive.com, linux-kernel@vger.kernel.org,
	peterlin@andestech.com
Subject: Re: [PATCH v3 0/4] riscv: Separate vendor extensions from standard extensions
Date: Tue, 23 Jul 2024 12:58:36 +0000	[thread overview]
Message-ID: <172173951651.10883.11801254450675807570.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240719-support_vendor_extensions-v3-0-0af7587bbec0@rivosinc.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Fri, 19 Jul 2024 09:15:17 -0700 you wrote:
> All extensions, both standard and vendor, live in one struct
> "riscv_isa_ext". There is currently one vendor extension, xandespmu, but
> it is likely that more vendor extensions will be added to the kernel in
> the future. As more vendor extensions (and standard extensions) are
> added, riscv_isa_ext will become more bloated with a mix of vendor and
> standard extensions.
> 
> [...]

Here is the summary with links:
  - [v3,1/4] riscv: Extend cpufeature.c to detect vendor extensions
    https://git.kernel.org/riscv/c/23c996fc2bc1
  - [v3,2/4] riscv: Add vendor extensions to /proc/cpuinfo
    https://git.kernel.org/riscv/c/9448d9accdd8
  - [v3,3/4] riscv: Introduce vendor variants of extension helpers
    https://git.kernel.org/riscv/c/0f2425411101
  - [v3,4/4] riscv: cpufeature: Extract common elements from extension checking
    https://git.kernel.org/riscv/c/d4c8d79f5199

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: Charlie Jenkins <charlie@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	conor.dooley@microchip.com, evan@rivosinc.com,
	andy.chiu@sifive.com, linux-kernel@vger.kernel.org,
	peterlin@andestech.com
Subject: Re: [PATCH v3 0/4] riscv: Separate vendor extensions from standard extensions
Date: Tue, 23 Jul 2024 12:58:36 +0000	[thread overview]
Message-ID: <172173951651.10883.11801254450675807570.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240719-support_vendor_extensions-v3-0-0af7587bbec0@rivosinc.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Fri, 19 Jul 2024 09:15:17 -0700 you wrote:
> All extensions, both standard and vendor, live in one struct
> "riscv_isa_ext". There is currently one vendor extension, xandespmu, but
> it is likely that more vendor extensions will be added to the kernel in
> the future. As more vendor extensions (and standard extensions) are
> added, riscv_isa_ext will become more bloated with a mix of vendor and
> standard extensions.
> 
> [...]

Here is the summary with links:
  - [v3,1/4] riscv: Extend cpufeature.c to detect vendor extensions
    https://git.kernel.org/riscv/c/23c996fc2bc1
  - [v3,2/4] riscv: Add vendor extensions to /proc/cpuinfo
    https://git.kernel.org/riscv/c/9448d9accdd8
  - [v3,3/4] riscv: Introduce vendor variants of extension helpers
    https://git.kernel.org/riscv/c/0f2425411101
  - [v3,4/4] riscv: cpufeature: Extract common elements from extension checking
    https://git.kernel.org/riscv/c/d4c8d79f5199

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-07-23 12:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 16:15 [PATCH v3 0/4] riscv: Separate vendor extensions from standard extensions Charlie Jenkins
2024-07-19 16:15 ` Charlie Jenkins
2024-07-19 16:15 ` [PATCH v3 1/4] riscv: Extend cpufeature.c to detect vendor extensions Charlie Jenkins
2024-07-19 16:15   ` Charlie Jenkins
2024-07-19 16:15 ` [PATCH v3 2/4] riscv: Add vendor extensions to /proc/cpuinfo Charlie Jenkins
2024-07-19 16:15   ` Charlie Jenkins
2024-07-19 16:15 ` [PATCH v3 3/4] riscv: Introduce vendor variants of extension helpers Charlie Jenkins
2024-07-19 16:15   ` Charlie Jenkins
2024-07-19 16:15 ` [PATCH v3 4/4] riscv: cpufeature: Extract common elements from extension checking Charlie Jenkins
2024-07-19 16:15   ` Charlie Jenkins
2024-07-22 19:32 ` [PATCH v3 0/4] riscv: Separate vendor extensions from standard extensions Andrew Jones
2024-07-22 19:32   ` Andrew Jones
2024-07-22 20:23   ` Charlie Jenkins
2024-07-22 20:23     ` Charlie Jenkins
2024-07-22 23:45     ` Palmer Dabbelt
2024-07-22 23:45       ` Palmer Dabbelt
2024-07-23 12:58 ` patchwork-bot+linux-riscv [this message]
2024-07-23 12:58   ` 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=172173951651.10883.11801254450675807570.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=andy.chiu@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=evan@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterlin@andestech.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.