From: Bo Gan <ganboing@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, samuel.holland@sifive.com,
david@redhat.com, palmer@dabbelt.com, pjw@kernel.org,
gaohan@iscas.ac.cn, me@ziyao.cc, lizhi2@eswincomputing.com,
hal.feng@starfivetech.com, marcel@ziswiler.com, kernel@esmil.dk,
devicetree@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/3] riscv: support EIC770X/JH7110 noncoherent devices with XPbmtUC
Date: Thu, 3 Sep 2026 19:15:14 -0700 [thread overview]
Message-ID: <1a7cf36f-aef3-4837-8390-5d063fab3e14@gmail.com> (raw)
In-Reply-To: <20260324-marshland-stretch-cc21ae7fdc2e@spud>
On 3/24/26 10:49, Conor Dooley wrote:
> On Mon, Mar 23, 2026 at 04:08:33PM -0700, Bo Gan wrote:
>> Hi All,
>>
>> Any suggestions/comments on this?
>
> I'll get to it at some point, just busy sorry!
Hi Conor,
It's been quite a while, and I almost forgot about this. Any new
suggestions? Comments?
Bo
prev parent reply other threads:[~2026-09-04 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 6:03 [RFC PATCH v2 0/3] riscv: support EIC770X/JH7110 noncoherent devices with XPbmtUC Bo Gan
2026-03-16 6:03 ` [RFC PATCH v2 1/3] riscv: alternatives: support auipc+load pair Bo Gan
2026-03-16 6:03 ` [RFC PATCH v2 2/3] riscv: errata: sifive: support auipc/load pair in patched alternatives Bo Gan
2026-03-16 6:03 ` [RFC PATCH v2 3/3] riscv: errata: sifive: Add an "errata" to simulate Svpbmt on cores without Bo Gan
2026-03-23 23:08 ` [RFC PATCH v2 0/3] riscv: support EIC770X/JH7110 noncoherent devices with XPbmtUC Bo Gan
2026-03-24 17:49 ` Conor Dooley
2026-09-04 2:15 ` Bo Gan [this message]
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=1a7cf36f-aef3-4837-8390-5d063fab3e14@gmail.com \
--to=ganboing@gmail.com \
--cc=conor@kernel.org \
--cc=david@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=gaohan@iscas.ac.cn \
--cc=hal.feng@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=linux-riscv@lists.infradead.org \
--cc=lizhi2@eswincomputing.com \
--cc=marcel@ziswiler.com \
--cc=me@ziyao.cc \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=samuel.holland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox