From: "François Revol" <revol@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] When will the Q35 chipset be merged into Qemu mainstream
Date: Wed, 24 Aug 2011 22:46:33 +0200 [thread overview]
Message-ID: <4E556329.5000003@free.fr> (raw)
In-Reply-To: <20110824193643.824b4f7b@shadowfax.no-ip.com>
Le -10/01/-28163 20:59, Adnan Khaleel a écrit :
> PCI express support has been made available for quite sometime now with patches from Isaku Yamahata for the Q35 chipset for Qemu 0.12 and then for Qemu 0.14. However, Qemu 0.15 has been released but support for the Q35 chipset is still not officially included.
>
> At what point will Qemu merge the Q35 chipset code for PCIexpress?
I'm afraid you're chasing the wrong rabbit here if you send patches
against releases.
Development happens on the git tree, so patches should be against HEAD.
Sending patches against (old by definition) releases implies someone
must do the merge since usually many things have diverged since then.
Specially with the recent move to Glib and other qdevice or whatever API.
So you'll maximize luck by sending patches against HEAD as it removes
most merging trouble.
Another way is to fork the git tree, apply your current patch, handle
the merge yourself and send pull request instead of the patch.
Still, I recall having to wait 3 year for my wacom tablet fix (which was
just a fix) to be applied, so be patient :P
François.
prev parent reply other threads:[~2011-08-24 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 19:36 [Qemu-devel] When will the Q35 chipset be merged into Qemu mainstream Adnan Khaleel
2011-08-24 20:46 ` François Revol [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=4E556329.5000003@free.fr \
--to=revol@free.fr \
--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).