From: Juan Quintela <quintela@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-trivial] [PATCH] Separate function types from opaque types in include/qemu/typedefs.h
Date: Thu, 22 Jun 2017 19:03:13 +0200 [thread overview]
Message-ID: <87injo6jla.fsf@secure.mitica> (raw)
In-Reply-To: <20170622184255.2d44e3bd@bahia.lab.toulouse-stg.fr.ibm.com> (Greg Kurz's message of "Thu, 22 Jun 2017 18:42:55 +0200")
Greg Kurz <groug@kaod.org> wrote:
> On Thu, 22 Jun 2017 17:14:08 +0100
> Peter Maydell <peter.maydell@linaro.org> wrote:
>
>> On 22 June 2017 at 17:06, Greg Kurz <groug@kaod.org> wrote:
>> > Function types cannot reside in the same sorted list as opaque types since
>> > they may depend on a type which would be defined later.
>> >
>> > Of course, the same problem could arise if a function type depends on
>> > another function type with greater alphabetical order. Hopefully we
>> > don't have that at this time.
>>
>> The other approach would be to put function types somewhere
>> else and leave typedefs.h for the simple 'opaque types
>> for structures' that it was started as.
>>
>> For instance we have include/qemu/fprintf-fn.h as a precedent.
>>
>
> Indeed, and I'm not quite sure why Juan decided to put these types into
> typedefs.h instead of a dedicated header file in include/migration... is
> it only because it was the quickest fix ?
All other typedefs were defined there. I can create a different include
file, but I think that is "overengineering", no? They are typedefs,
just not of structs. But I agree that they are the only ones.
Later, Juan.
WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Separate function types from opaque types in include/qemu/typedefs.h
Date: Thu, 22 Jun 2017 19:03:13 +0200 [thread overview]
Message-ID: <87injo6jla.fsf@secure.mitica> (raw)
In-Reply-To: <20170622184255.2d44e3bd@bahia.lab.toulouse-stg.fr.ibm.com> (Greg Kurz's message of "Thu, 22 Jun 2017 18:42:55 +0200")
Greg Kurz <groug@kaod.org> wrote:
> On Thu, 22 Jun 2017 17:14:08 +0100
> Peter Maydell <peter.maydell@linaro.org> wrote:
>
>> On 22 June 2017 at 17:06, Greg Kurz <groug@kaod.org> wrote:
>> > Function types cannot reside in the same sorted list as opaque types since
>> > they may depend on a type which would be defined later.
>> >
>> > Of course, the same problem could arise if a function type depends on
>> > another function type with greater alphabetical order. Hopefully we
>> > don't have that at this time.
>>
>> The other approach would be to put function types somewhere
>> else and leave typedefs.h for the simple 'opaque types
>> for structures' that it was started as.
>>
>> For instance we have include/qemu/fprintf-fn.h as a precedent.
>>
>
> Indeed, and I'm not quite sure why Juan decided to put these types into
> typedefs.h instead of a dedicated header file in include/migration... is
> it only because it was the quickest fix ?
All other typedefs were defined there. I can create a different include
file, but I think that is "overengineering", no? They are typedefs,
just not of structs. But I agree that they are the only ones.
Later, Juan.
next prev parent reply other threads:[~2017-06-22 17:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 16:06 [Qemu-trivial] [PATCH] Separate function types from opaque types in include/qemu/typedefs.h Greg Kurz
2017-06-22 16:06 ` [Qemu-devel] " Greg Kurz
2017-06-22 16:14 ` [Qemu-trivial] " Peter Maydell
2017-06-22 16:14 ` Peter Maydell
2017-06-22 16:42 ` [Qemu-trivial] " Greg Kurz
2017-06-22 16:42 ` Greg Kurz
2017-06-22 17:03 ` Juan Quintela [this message]
2017-06-22 17:03 ` Juan Quintela
2017-06-22 17:22 ` [Qemu-trivial] " Peter Maydell
2017-06-22 17:22 ` [Qemu-devel] " Peter Maydell
2017-06-22 17:25 ` [Qemu-trivial] " Dr. David Alan Gilbert
2017-06-22 17:25 ` [Qemu-devel] " Dr. David Alan Gilbert
2017-06-22 17:46 ` [Qemu-trivial] " Greg Kurz
2017-06-22 17:46 ` Greg Kurz
2017-06-22 17:50 ` [Qemu-trivial] " Dr. David Alan Gilbert
2017-06-22 17:50 ` Dr. David Alan Gilbert
2017-06-22 18:08 ` [Qemu-trivial] " Thomas Huth
2017-06-22 18:08 ` Thomas Huth
2017-06-22 18:11 ` [Qemu-trivial] " Peter Maydell
2017-06-22 18:11 ` Peter Maydell
2017-06-22 18:34 ` [Qemu-trivial] " Dr. David Alan Gilbert
2017-06-22 18:34 ` Dr. David Alan Gilbert
2017-06-22 19:23 ` [Qemu-trivial] " Greg Kurz
2017-06-22 19:23 ` Greg Kurz
2017-06-26 9:27 ` [Qemu-trivial] " Dr. David Alan Gilbert
2017-06-26 9:27 ` Dr. David Alan Gilbert
2017-06-23 7:11 ` [Qemu-trivial] " Markus Armbruster
2017-06-23 7:11 ` Markus Armbruster
2017-06-28 9:32 ` [Qemu-trivial] " Juan Quintela
2017-06-28 9:32 ` [Qemu-devel] " Juan Quintela
2017-06-23 7:04 ` [Qemu-trivial] " Markus Armbruster
2017-06-23 7:04 ` Markus Armbruster
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=87injo6jla.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.