From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Naghl-0006Pm-Vn for qemu-devel@nongnu.org; Thu, 28 Jan 2010 21:35:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Naghg-0006OU-GT for qemu-devel@nongnu.org; Thu, 28 Jan 2010 21:35:28 -0500 Received: from [199.232.76.173] (port=59022 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Naghg-0006OR-AG for qemu-devel@nongnu.org; Thu, 28 Jan 2010 21:35:24 -0500 Received: from smtp-out.google.com ([216.239.33.17]:46314) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Naghf-0006Rz-GF for qemu-devel@nongnu.org; Thu, 28 Jan 2010 21:35:24 -0500 Received: from kpbe19.cbf.corp.google.com (kpbe19.cbf.corp.google.com [172.25.105.83]) by smtp-out.google.com with ESMTP id o0T2ZJtE030184 for ; Fri, 29 Jan 2010 02:35:19 GMT Received: from iwn10 (iwn10.prod.google.com [10.241.68.74]) by kpbe19.cbf.corp.google.com with ESMTP id o0T2ZHLa020476 for ; Thu, 28 Jan 2010 18:35:18 -0800 Received: by iwn10 with SMTP id 10so1436649iwn.22 for ; Thu, 28 Jan 2010 18:35:17 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4B5B7AFB.9040506@codemonkey.ws> References: <195c7a901001210827i29b91f30p3a80c2a8a0c2b4bb@mail.gmail.com> <4B5B7AFB.9040506@codemonkey.ws> Date: Thu, 28 Jan 2010 18:35:16 -0800 Message-ID: <60cad3f1001281835o1da4f17bjba67fc500411b15b@mail.gmail.com> Subject: Re: [Qemu-devel] Merge qemu android From: David Turner Content-Type: multipart/alternative; boundary=001636d342556a3edc047e447c01 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Bastien ROUCARIES , qemu-devel@nongnu.org --001636d342556a3edc047e447c01 Content-Type: text/plain; charset=ISO-8859-1 Anthony is right, and unfortunately the Android team doesn't have the bandwidth to support sending patches to upstream at the moment. Note that our version of QEMU is a rather complex mix of 0.8.2 and upstream. I routinely cherry pick upstream improvements and incorporate them to the codebase. However, I'm also pretty conservative and try to avoid stuff we don't depend on and which risk breaking other stuff easily so many parts don't get in, or are implemented differently. Also, many, many things in the Android emulator codebase have very little value for upstream qemu, imho. Bastien, what specific features are you interested in ? I can still have a look at what would be required to generate the corresponding upstream patch. On Sat, Jan 23, 2010 at 2:40 PM, Anthony Liguori wrote: > On 01/21/2010 10:27 AM, Bastien ROUCARIES wrote: > >> Hi, >> >> What is the step in order to get qemu android merged mainline ? >> >> http://android.git.kernel.org/?p=platform/external/qemu.git;a=summary >> >> > > Send patches. > > It's very difficult to merge downstream code unless that entire downstream > is committed to working through upstream. I'd suggest encouraging the > Android developers to commit to pushing all of the functionality upstream > before going down this path. > > Regards, > > Anthony Liguori > > Regards >> >> Bastien >> >> >> >> > > > > --001636d342556a3edc047e447c01 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Anthony is right, and unfortunately the Android team doesn't have the b= andwidth to support sending patches to upstream
at the moment.

<= /div>
Note that our version of QEMU is a rather complex mix of 0.8.2 an= d upstream. I routinely cherry pick upstream improvements
and incorporate them to the codebase. However, I'm also pretty conserva= tive and try to avoid stuff we don't depend on and
which risk= breaking other stuff easily so many parts don't get in, or are impleme= nted differently.

Also, many, many things in the Android emulator codebase hav= e very little value for upstream qemu, imho.

Basti= en, what specific features are you interested in ? I can still have a look = at what would be required to generate the
corresponding upstream patch.

On Sat, Jan 23, 2010 at 2:40 PM, Anthony Liguori <anthony@codemonkey.= ws> wrote:
On 01/21/2010 10:27 AM, Bastien ROUCARIES wrote:
Hi,

What is the step in order to get qemu android merged mainline ?

http://android.git.kernel.org/?p=3Dplatform/e= xternal/qemu.git;a=3Dsummary
=A0

Send patches.

It's very difficult to merge downstream code unless that entire downstr= eam is committed to working through upstream. =A0I'd suggest encouragin= g the Android developers to commit to pushing all of the functionality upst= ream before going down this path.

Regards,

Anthony Liguori

Regards

Bastien


=A0




--001636d342556a3edc047e447c01--