public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: linux-riscv@lists.infradead.org,
	"Palmer Dabbelt" <palmer@rivosinc.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Anup Patel" <anup@brainfault.org>,
	"Mayuresh Chitale" <mchitale@ventanamicro.com>
Cc: Atish Patra <atishp@atishpatra.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Jessica Clarke <jrtc27@jrtc27.com>
Subject: [PATCH v3 0/2] Zicbom block size fixes and cleanups
Date: Tue,  6 Sep 2022 09:45:07 +0200	[thread overview]
Message-ID: <20220906074509.928865-1-ajones@ventanamicro.com> (raw)

I collected a couple patches that were necessary for another series.
Since some changes were required to the second patch I'm posting in
case it simplifies things.

v3:
 - Applied Anup's move change first to ensure the second patch can
   compile with Heiko's change.

v2:
 - First attempt at sending a fixed-up version of the second patch,
   which mistakenly included Heiko's change without Anup's change.

v1:
 - The original patches on the list
   1. [PATCH v2 2/4] RISC-V: Move riscv_init_cbom_blocksize() to cacheflush.c
      20220829125226.511564-5-apatel@ventanamicro.com
   2. [PATCH v2] RISC-V: Clean up the Zicbom block size probing
      20220812154010.18280-1-palmer@rivosinc.com

Anup Patel (1):
  RISC-V: Move riscv_init_cbom_blocksize() to cacheflush.c

Palmer Dabbelt (1):
  RISC-V: Clean up the Zicbom block size probing

 arch/riscv/errata/thead/errata.c    |  1 +
 arch/riscv/include/asm/cacheflush.h |  2 ++
 arch/riscv/kernel/setup.c           |  2 +-
 arch/riscv/mm/cacheflush.c          | 40 +++++++++++++++++++++++++++++
 arch/riscv/mm/dma-noncoherent.c     | 40 ++---------------------------
 5 files changed, 46 insertions(+), 39 deletions(-)

-- 
2.37.2


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2022-09-06  7:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  7:45 Andrew Jones [this message]
2022-09-06  7:45 ` [PATCH v3 1/2] RISC-V: Move riscv_init_cbom_blocksize() to cacheflush.c Andrew Jones
2022-09-06  7:51   ` Conor.Dooley
2022-09-06  7:53   ` Heiko Stübner
2022-09-06  7:45 ` [PATCH v3 2/2] RISC-V: Clean up the Zicbom block size probing Andrew Jones
2022-09-06  8:33   ` Heiko Stübner
2022-09-06 15:34   ` Nathan Chancellor
     [not found]   ` <CAOnJCULO-pSNgsvXMbCiOi72jJmOvB_UGGw87psynbXgo1K_3A@mail.gmail.com>
2022-09-08  7:11     ` Andrew Jones
2022-09-08  7:50       ` Conor.Dooley
2022-09-08  7:53       ` Atish Patra
2022-09-08  8:10       ` Heiko Stübner
2022-09-08 10:05         ` Andrew Jones
2022-09-08 10:48         ` Jessica Clarke
2022-09-08 11:22           ` Andrew Jones
2022-09-08 11:37             ` Heiko Stübner
2022-09-08 17:57             ` Atish Patra
2022-09-08 23:14 ` [PATCH v3 0/2] Zicbom block size fixes and cleanups Palmer Dabbelt
2022-09-08 23:20   ` Conor.Dooley

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=20220906074509.928865-1-ajones@ventanamicro.com \
    --to=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=atishp@atishpatra.org \
    --cc=conor.dooley@microchip.com \
    --cc=heiko@sntech.de \
    --cc=jrtc27@jrtc27.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mchitale@ventanamicro.com \
    --cc=nathan@kernel.org \
    --cc=palmer@rivosinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox