From: "Alex Bennée" <alex.bennee@linaro.org>
To: Gleb Popov <arrowd@freebsd.org>
Cc: qemu-devel@nongnu.org
Subject: Re: Upstreaming of the Elbrus2000 architecture support
Date: Mon, 23 Feb 2026 13:35:41 +0000 [thread overview]
Message-ID: <87sear4m6q.fsf@draig.linaro.org> (raw)
In-Reply-To: <CALH631=92UznqkD25FszdAAFdm_0GAvpM-m1qYW1yeyQ1Lm6Kg@mail.gmail.com> (Gleb Popov's message of "Mon, 23 Feb 2026 10:44:34 +0300")
Gleb Popov <arrowd@freebsd.org> writes:
> Hello QEMU devs.
>
> MCST, a company behind the Elbrus2000 (e2k) architecture has
> open-sourced their QEMU fork that features e2k support [1]. I
> volunteered to help them get their work merged upstream. I realize
> that it might take a decent amount of time and labor, but I'm fully
> committed to this. On the MCST part they dispatched a developer team
> (CCed) to help in reviewing, answer questions and provide future code
> maintenance once it gets merged.
>
> So, if the whole idea sounds interesting to the QEMU community, what
> would be our first steps?
I think your first problem is finding people that can review and merge
the code. As MCST is on the sanctions list a potentially large section
of the regular contributors can't be involved in code review.
You may find a maintainer willing to process the PRs after they have
been reviewed but IANAL so check with your own counsel. It would be
worth making sure you have a plan before investing a lot of work into
re-basing and posting.
>
> [1] https://git.openelbrus.ru/mcst/qemu
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2026-02-23 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 7:44 Upstreaming of the Elbrus2000 architecture support Gleb Popov
2026-02-23 13:35 ` Alex Bennée [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=87sear4m6q.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=arrowd@freebsd.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.