All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Networking patches queue
Date: Thu, 28 May 2009 10:56:50 -0500	[thread overview]
Message-ID: <4A1EB442.1060006@us.ibm.com> (raw)
In-Reply-To: <1243525873.18588.11.camel@blaa>

Mark McLoughlin wrote:
> On Thu, 2009-05-28 at 10:28 -0500, Anthony Liguori wrote:
>   
>> If the first 6 patches of Jan's series are ready to apply, wouldn't it
>> make sense for him to submit that as a separate series?  In the very
>> least, I'd like an Ack from Jan before applying his series partially.
>>     
>
> I would have thought that was one of the benefits of a clean, bisectable
> patch series - that a maintainer could choose to partially apply them.
>
> I know when I send a patch series, I'm fully prepared for that to happen
> and would much rather see them applied partially if possible, rather
> than re-send the whole series.
>
> (Where partially means 1-N not randomly choosing a subset of patches)
>   

I used to do that, but not everyone likes it.

>> I just got the tail end of your series before heading off on travel on
>> Friday.  It still needs review and testing.
>>     
>
> Okay, that's perfectly reasonable.
>
> I got the impression you would like (at some point) to be able to have
> others to act as a funnel for specific areas. I'm just testing the
> water :-)
>   

Yes, that's what I was hinting at below :-)

>> Of course, if a patches series included test cases for the functionality
>> it was implementing, it would certainly go a far way into reducing the
>> amount of time it took to test those patches :-)
>>     
>
> That's a funny way of observing "we really should have a networking test
> suite".
>
> Would "this tree passes kvm-autotest's networking tests" help matters?
> If so, I'm sure that could be organised ...
>   

Does kvm-autotest have networking tests?

I know there's some concern about the time it takes for patches to get
applied.  IMHO, the best way to improve that it to get a stronger set of
functional tests.  I have a set I've been working on but it's on my
other laptop which I cannot reach ATM :-/

As has been discussed before, I'm looking for finer grain functional
tests than the installation tests that kvm-autotest is providing now. 
I'm not saying that this series requires submitting a test suite first,
but rather that if you're interested in seeing networking advance more
rapidly, a good investment would be to build out a better test
infrastructure for it.

Regards,

Anthony Liguori

  reply	other threads:[~2009-05-28 15:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 15:19 [Qemu-devel] Networking patches queue Mark McLoughlin
2009-05-28 15:28 ` [Qemu-devel] " Anthony Liguori
2009-05-28 15:51   ` Jan Kiszka
2009-05-28 16:57     ` Mark McLoughlin
2009-05-28 20:26       ` Anthony Liguori
2009-05-28 17:01     ` Glauber Costa
2009-05-28 17:19       ` Jan Kiszka
2009-05-28 19:10       ` Jan Kiszka
2009-05-28 15:51   ` Mark McLoughlin
2009-05-28 15:56     ` Anthony Liguori [this message]
2009-05-28 16:52       ` Mark McLoughlin
2009-05-31 20:58       ` Dor Laor
2009-06-09 21:43 ` Mark McLoughlin
2009-06-10 23:08   ` Anthony Liguori
2009-06-11  1:27   ` Anthony Liguori
2009-06-11  8:34     ` Mark McLoughlin
2009-06-11  8:38   ` Gerd Hoffmann
2009-06-11  9:42     ` [Qemu-devel] [PATCH] Fix xilinx_ethlite breakage by 4f1c942b7f Jan Kiszka
2009-06-11 10:48       ` [Qemu-devel] " Mark McLoughlin
2009-06-11 11:48   ` [Qemu-devel] Re: Networking patches queue Paul Brook
2009-06-11 12:50     ` Anthony Liguori

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=4A1EB442.1060006@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=markmc@redhat.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 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.