public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Dmitry Kasatkin <dmitry.kasatkin@huawei.com>
Cc: "cl-cheri-discuss@lists.cam.ac.uk"
	<cl-cheri-discuss@lists.cam.ac.uk>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"cl-cheribsd-discuss@lists.cam.ac.uk" 
	<cl-cheribsd-discuss@lists.cam.ac.uk>,
	Wang Kui <wang.kui1@huawei.com>,
	Jan Erik Ekberg <jan.erik.ekberg@huawei.com>,
	"Horsch, Julian" <julian.horsch@aisec.fraunhofer.de>,
	"Auer, Lukas" <lukas.auer@aisec.fraunhofer.de>,
	"Ahlrichs, Vincent" <vincent.ahlrichs@aisec.fraunhofer.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: RISC-V CHERI port
Date: Wed, 28 Sep 2022 14:00:33 +0100	[thread overview]
Message-ID: <YzRFcaNFZ7LPzrLH@wendy> (raw)
In-Reply-To: <1c0ba05578f1487980b071da1377fb3f@huawei.com>

On Wed, Sep 28, 2022 at 12:54:40PM +0000, Dmitry Kasatkin wrote:
> Hi,
> 
> I would like to inform here that our Cheri Linux for RISC-V work has been open sourced.

That sounds great - but unfortunately I do not know what "Cheri Linux"
is or what the "RISC-V work" entails. Do you maybe have some links to
relevant material that you can share or a brief explanation of the
benefits?

I can only assume it is this? https://github.com/cheri-linux/linux

Is it something you intend upstreaming?

Thanks,
Conor.


  reply	other threads:[~2022-09-28 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 12:54 RISC-V CHERI port Dmitry Kasatkin
2022-09-28 13:00 ` Conor Dooley [this message]
2022-09-28 13:04 ` Dmitry Kasatkin

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=YzRFcaNFZ7LPzrLH@wendy \
    --to=conor.dooley@microchip.com \
    --cc=cl-cheri-discuss@lists.cam.ac.uk \
    --cc=cl-cheribsd-discuss@lists.cam.ac.uk \
    --cc=dmitry.kasatkin@huawei.com \
    --cc=jan.erik.ekberg@huawei.com \
    --cc=julian.horsch@aisec.fraunhofer.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lukas.auer@aisec.fraunhofer.de \
    --cc=vincent.ahlrichs@aisec.fraunhofer.de \
    --cc=wang.kui1@huawei.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