qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: Glauber Costa <glommer@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure
Date: Thu, 11 Jun 2009 10:33:12 +0200	[thread overview]
Message-ID: <87vdn3mapj.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <20090610220540.GE23525@kos.to> (Riku Voipio's message of "Thu\, 11 Jun 2009 01\:05\:40 +0300")

Riku Voipio <riku.voipio@iki.fi> writes:
Hi,

> On Wed, Jun 10, 2009 at 01:56:40PM -0300, Glauber Costa wrote:
>> > >> because mainline qemu is lacking a linux-user maintainer.
>> > > I believe if you can guarantee (through proper testing) the stability of maemo
>> > > tree, and poke for review the specific parts that may affect the rest ot the world,
>> > > then it should be fine to just pull it.
>
>> > At least, this would be better than what we have currently. Please note
>> > also that "proper testing" is hard imho. It depends also on host/guest
>> > systems used to test.
>
>> it is hard for everybody, not just qemu user. Since you guys are the main
>> user of it, if you are happy with the state of things, and it is isolated enough from
>> the rest of qemu not to break it very frequently, we should be fine.
>
> Generally we use tests from ltp testsuite since they have nice tests for most
> syscalls. However, the testing is not quite systematic, an particularry combinations
> of host/target glibc appear to create a mess..

Do you have a list of the syscalls/ltp testcases you're testing ? I've
made a list, only wants to compare :)

>
> That said, the changes are highly contained under linux-user/, in the current tree
> there is only one patch (GUEST_BASE support) that touches outside parts.
>
>> > Having an "official" maintainer means having someone being able to give
>> > his final word if people disagree on how to fix a bug.
>
>> One of you should step up and do it.
>
> If nobody objects, I can.

I bet you have more time than me to work on qemu so that's
fine. Nevertheless, I can provide help if needed.


Arnaud

  reply	other threads:[~2009-06-11  8:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 21:26 [Qemu-devel] [PATCH 0/2] linux-user: fix build error against older glibcs Eduardo Habkost
2009-06-09 21:26 ` [Qemu-devel] [PATCH 1/2] linux-user/syscall.c: define _ATFILE_SOURCE Eduardo Habkost
2009-06-09 21:26 ` [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure Eduardo Habkost
2009-06-09 22:06   ` Arnaud Patard
2009-06-10 14:12     ` Eduardo Habkost
2009-06-10 14:39       ` Arnaud Patard
2009-06-10 19:10         ` Eduardo Habkost
2009-06-10 21:48           ` Riku Voipio
2009-06-10 22:09             ` Eduardo Habkost
2009-06-11 15:14               ` Riku Voipio
2009-06-10 16:07       ` Riku Voipio
2009-06-10 16:20         ` Glauber Costa
2009-06-10 16:30           ` Arnaud Patard
2009-06-10 16:56             ` Glauber Costa
2009-06-10 22:05               ` Riku Voipio
2009-06-11  8:33                 ` Arnaud Patard [this message]
2009-06-11 15:09                   ` Riku Voipio
2009-06-12  8:30                     ` ltp vs linux-user (was: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure) Arnaud Patard
2009-06-11 11:27                 ` [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure vibi sreenivasan
2009-06-12 13:24                 ` vibi sreenivasan
2009-06-10 15:03     ` Glauber Costa
2009-06-10 21:53       ` Riku Voipio

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=87vdn3mapj.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=glommer@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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).