From: Mark McLoughlin <markmc@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.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 16:51:13 +0100 [thread overview]
Message-ID: <1243525873.18588.11.camel@blaa> (raw)
In-Reply-To: <4A1EADB4.2060106@us.ibm.com>
On Thu, 2009-05-28 at 10:28 -0500, Anthony Liguori wrote:
> Mark McLoughlin wrote:
> > Hi Anthony,
> >
> > Recently, Jan has posted 11 networking patches and I've posted 17, so I
> > thought I'd push out a tree with these queued up. Perhaps you want to
> > pull from there?
> >
> > Some notes:
> >
> > - I've taken the first 6 of Jan's patches, but left 7-11 for now; see
> > the review comments I just posted. I expect Jan will be able to
> > fix them up fairly quickly
> >
>
> 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've tried my best to fix up the param checking saga by reverting
> > Kevin's patch, going with Jan's rollback to something closer to
> > what was there originally and applying a small fixup patch
> >
> > - Not all of these patches are completely isolated to networking
> > code - e.g. the fork_exec() patch adds a SIGCHLD handler
> >
> > - I haven't reviewed the slirp changes in great detail, but they
> > look okay at a glance
> >
>
> 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 :-)
> 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 ...
Cheers,
Mark.
next prev parent reply other threads:[~2009-05-28 15:51 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 [this message]
2009-05-28 15:56 ` Anthony Liguori
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=1243525873.18588.11.camel@blaa \
--to=markmc@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.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.