qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Michael S Tsirkin <mst@redhat.com>,
	Victor Kaplansky <victork@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tests: Test IPv6 and ppc64 in the PXE tester
Date: Wed, 28 Sep 2016 08:38:41 +0200	[thread overview]
Message-ID: <358bbba8-845d-ad36-e30a-db717fb52617@redhat.com> (raw)
In-Reply-To: <20160928015900.GB18880@umbus>

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

On 28.09.2016 03:59, David Gibson wrote:
> On Tue, Sep 27, 2016 at 09:17:19AM +0200, Thomas Huth wrote:
>> On 27.09.2016 06:17, David Gibson wrote:
>>> On Mon, Sep 26, 2016 at 10:17:46PM +0200, Thomas Huth wrote:
[...]
>>>> diff --git a/tests/pxe-test.c b/tests/pxe-test.c
>>>> index b2cc355..0bdb7a1 100644
>>>> --- a/tests/pxe-test.c
>>>> +++ b/tests/pxe-test.c
>>>> @@ -21,14 +21,14 @@
>>>>  
>>>>  static const char *disk = "tests/pxe-test-disk.raw";
>>>>  
>>>> -static void test_pxe_one(const char *params)
>>>> +static void test_pxe_one(const char *params, bool ipv6)
>>>
>>> Is it wise to keep the "PXE" name.  OF style netbooting isn't really
>>> PXE in the sense of the Intel PXE spec, although it overlaps in the
>>> underlying protocols used.
>>
>> Strictly speaking, you're right. But the overlap from the networking
>> protocol point of view is 95%, I'd guess, basically you can say that:
>>
>>  PXE = TFTP + DHCP + some few DHCP extensions
> 
> (aside on subtle English usage at [0] if you're interested)
[...]
> [0] A native speaker would probably say "a few" DHCP extensions here.
> "some few", oddly enough, reads as very slight sarcasm implying that
> there are actually quite a lot of extensions, or at least more than
> you'd expect.

Oh, good to know, that's the things that you miss as a non-native
speaker ... so I actually really meant "a few" here (though some of the
extensions are IMHO rather strange).

 Thomas



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2016-09-28  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 20:17 [Qemu-devel] [PATCH] tests: Test IPv6 and ppc64 in the PXE tester Thomas Huth
2016-09-27  4:17 ` David Gibson
2016-09-27  7:17   ` Thomas Huth
2016-09-28  1:59     ` David Gibson
2016-09-28  6:38       ` Thomas Huth [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=358bbba8-845d-ad36-e30a-db717fb52617@redhat.com \
    --to=thuth@redhat.com \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=jan.kiszka@siemens.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=victork@redhat.com \
    /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).