From: "Alex Bennée" <alex.bennee@linaro.org>
To: Chris Hoy <hoychris01@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Fully operable build post
Date: Thu, 28 May 2020 09:48:44 +0100 [thread overview]
Message-ID: <87mu5s4f83.fsf@linaro.org> (raw)
In-Reply-To: <CADAnahmxeveTRvoN9TN3qgi+_gy5PpSCULy+Cp3Rzj0gaE-p7A@mail.gmail.com>
Chris Hoy <hoychris01@gmail.com> writes:
> Hello all,
>
> I am proud to see that I have my barebones implementation of qemu finally
> working. After starting earlier this year, I have slowly made progress to
> fully integrate my kernel hardware into a gpu-passthrough vm. I went
> through many settings and templates from various sources and finally have
> something that works for me for a start and would be really interested in
> lining out my experiences. It is my observation that the documentation may
> be a bit unevenly distributed on the official page as far as templates go
> and so if I could help I would like to send my template through the
> official forum. Any help or advice with this would be greatly
> appreciated.
We have a top level page on contribution here:
https://www.qemu.org/contribute/
specifically the page:
https://wiki.qemu.org/Contribute/SubmitAPatch
goes into some detail on how to prepare, format and submit your patches.
Specifically it has notes on basing on master, breaking up a long series
for easy review and how to submit to the mailing list using git
send-email.
If there is something you don't understand in those pages or something
that could be made clearer then please ask for clarification here or on
the IRC channel.
>
> Best Regards
--
Alex Bennée
prev parent reply other threads:[~2020-05-28 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 19:52 Fully operable build post Chris Hoy
2020-05-28 8:48 ` 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=87mu5s4f83.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=hoychris01@gmail.com \
--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 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).