All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: tim@xen.org, xen-devel@lists.xen.org, keir@xen.org,
	ian.jackson@eu.citrix.com, ian.campbell@citrix.com
Subject: Re: [PATCH] xen: Minor modifications to platform.h to make it C++-friendly
Date: Mon, 23 Feb 2015 13:05:48 +0200	[thread overview]
Message-ID: <54EB098C.9000207@bitdefender.com> (raw)
In-Reply-To: <54EB14D902000078000626B5@mail.emea.novell.com>

On 02/23/2015 12:54 PM, Jan Beulich wrote:
>>>> @@ -152,24 +159,24 @@ struct xenpf_efi_runtime_call {
>>>>      xen_ulong_t status;
>>>>      union {
>>>>  #define XEN_EFI_GET_TIME_SET_CLEARS_NS 0x00000001
>>>> +        struct xenpf_efi_time {
>>>> +            uint16_t year;
>>>> +            uint8_t month;
>>>> +            uint8_t day;
>>>> +            uint8_t hour;
>>>> +            uint8_t min;
>>>> +            uint8_t sec;
>>>> +            uint32_t ns;
>>>> +            int16_t tz;
>>>> +            uint8_t daylight;
>>>> +        } set_time;
>>>> +
> 
> ... this should be moved out to file scope too, both for consistency
> and to avoid an eventual further adjustment going forward. Otoh
> I'm not convinced we need the headers to be C++ ready (nor am
> I convinced that there aren't any other obstacles preventing their
> unmodified use in C++). Co-maintainers, what do you think?

You're right, it's always better to be consistent. Will do.

As for the headers being C++ ready, there's already the precedent of at
least my previous patch "xenctrl: Make the headers C++ friendly":

http://www.gossamer-threads.com/lists/xen/devel/337788

where it turned out that there's at least one other serious user of Xen
with C++, Don Slutz.

I do understand and respect the fact that C++ is not a xen-devel target,
but I also believe that there are a very small number of changes that
could enlarge the Xen user base to include C++ developers, and that it
can be done in completely painless manner for all involved.


Thanks,
Razvan

  reply	other threads:[~2015-02-23 11:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23  9:34 [PATCH] xen: Minor modifications to platform.h to make it C++-friendly Razvan Cojocaru
2015-02-23 10:16 ` Jan Beulich
2015-02-23 10:31   ` Razvan Cojocaru
2015-02-23 10:54     ` Jan Beulich
2015-02-23 11:05       ` Razvan Cojocaru [this message]
2015-02-23 11:16         ` Jan Beulich
2015-02-23 11:09       ` Tim Deegan
2015-02-23 11:24         ` Jan Beulich
2015-02-23 11:24       ` Razvan Cojocaru

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=54EB098C.9000207@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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.