From: Christoph Hellwig <hch@lst.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
wefu@redhat.com, guoren@kernel.org, atishp@atishpatra.org,
anup@brainfault.org, mick@ics.forth.gr, samuel@sholland.org,
cmuellner@linux.com, philipp.tomsich@vrull.eu,
robh+dt@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Atish Patra <atish.patra@wdc.com>
Subject: Re: [PATCH v2 2/3] riscv: Implement Zicbom-based cache management operations
Date: Mon, 16 May 2022 08:00:33 +0200 [thread overview]
Message-ID: <20220516060033.GC12339@lst.de> (raw)
In-Reply-To: <20220511214132.2281431-3-heiko@sntech.de>
I'm still only getting one of three patches here, making it impossible
to review.
next prev parent reply other threads:[~2022-05-16 6:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 21:41 [PATCH v2 0/2] riscv: implement Zicbom-based CMO instructions + the t-head variant Heiko Stuebner
2022-05-11 21:41 ` [PATCH v2 1/3] dt-bindings: riscv: document cbom-block-size Heiko Stuebner
2022-05-12 4:18 ` Anup Patel
2022-05-13 10:28 ` Christoph Müllner
2022-05-18 0:25 ` Rob Herring
2022-05-18 8:22 ` Philipp Tomsich
2022-05-18 9:02 ` Heiko Stübner
2022-05-18 9:10 ` Anup Patel
2022-05-18 9:20 ` Philipp Tomsich
2022-05-25 15:14 ` Heiko Stübner
2022-05-11 21:41 ` [PATCH v2 2/3] riscv: Implement Zicbom-based cache management operations Heiko Stuebner
2022-05-12 4:19 ` Anup Patel
2022-05-13 13:38 ` Guo Ren
2022-05-16 6:00 ` Christoph Hellwig [this message]
2022-05-11 21:41 ` [PATCH v2 3/3] riscv: implement cache-management errata for T-Head SoCs Heiko Stuebner
2022-05-12 4:40 ` Anup Patel
2022-05-13 13:37 ` Guo Ren
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=20220516060033.GC12339@lst.de \
--to=hch@lst.de \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=atishp@atishpatra.org \
--cc=cmuellner@linux.com \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wefu@redhat.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;
as well as URLs for NNTP newsgroup(s).