From: Rob Landley <rob@landley.net>
To: Taylor Simpson <tsimpson@quicinc.com>,
Sid Manning <sidneym@quicinc.com>, Brian Cain <bcain@quicinc.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>
Cc: "ale@rev.ng" <ale@rev.ng>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"richard.henderson@linaro.org" <richard.henderson@linaro.org>,
"philmd@redhat.com" <philmd@redhat.com>
Subject: Re: [PATCH 01/20] Hexagon HVX (target/hexagon) README
Date: Thu, 25 Nov 2021 00:26:58 -0600 [thread overview]
Message-ID: <ee0ee7c5-22e5-2c79-695d-e66ae39bb5fb@landley.net> (raw)
In-Reply-To: <BYAPR02MB48863186EDD71439C60792A0DEE89@BYAPR02MB4886.namprd02.prod.outlook.com>
On 7/26/21 8:59 AM, Taylor Simpson wrote:
> We're working on system mode support for Hexagon, and we plan to upstream it when it is ready.
>
> Thanks,
> Taylor
Any progress on this? (Is there a way for outsiders to track the status?)
Thanks,
Rob
prev parent reply other threads:[~2021-11-25 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1625528074-19440-1-git-send-email-tsimpson@quicinc.com>
[not found] ` <1625528074-19440-2-git-send-email-tsimpson@quicinc.com>
[not found] ` <1b632e88-43d4-3034-cf7b-d42be056d842@landley.net>
[not found] ` <SN6PR02MB42054B50C60ABA378256492DB8159@SN6PR02MB4205.namprd02.prod.outlook.com>
[not found] ` <553c32e8-188c-5b2c-2f4a-a8cfd7b903a9@landley.net>
[not found] ` <BN7PR02MB4194007550E66EBE877625A6B8E19@BN7PR02MB4194.namprd02.prod.outlook.com>
[not found] ` <BYAPR02MB55091DE5B976956075B46FADBEE19@BYAPR02MB5509.namprd02.prod.outlook.com>
[not found] ` <8845de00-ddc7-86a3-600f-6ede81e168c2@landley.net>
2021-07-26 8:54 ` [PATCH 01/20] Hexagon HVX (target/hexagon) README Rob Landley
2021-07-26 13:59 ` Taylor Simpson
2021-07-28 8:11 ` Rob Landley
2021-11-25 6:26 ` Rob Landley [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=ee0ee7c5-22e5-2c79-695d-e66ae39bb5fb@landley.net \
--to=rob@landley.net \
--cc=ale@rev.ng \
--cc=bcain@quicinc.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sidneym@quicinc.com \
--cc=tsimpson@quicinc.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 read-only IMAP folder(s) and NNTP newsgroup(s).