From: Jens Axboe <axboe@kernel.dk>
To: Daniel Gollub <daniel.gollub@t-online.de>, fio@vger.kernel.org
Cc: Daniel Gollub <d.gollub@telekom.de>
Subject: Re: [PATCH 0/2] Make fio.h a bit more C++ safe
Date: Wed, 12 Feb 2014 08:26:46 -0700 [thread overview]
Message-ID: <52FB92B6.8070704@kernel.dk> (raw)
In-Reply-To: <1392216715-9539-1-git-send-email-d.gollub@telekom.de>
On 02/12/2014 07:51 AM, Daniel Gollub wrote:
> Following patches allow to include fio.h for a C++ based
> (external) ioengine to be compiled with g++.
>
> (Preparing two fio engines: one internal for CEPH RBD
> another external for CEPH FileStore)
>
> Daniel Gollub (2):
> Make file.h C++ safe by casting fio_file_flags
> Make parse.h C++ safe by avoiding "or" keyword
Thanks, applied both of them. You missed goptions.c for the ->or change,
caught that and fixed it.
--
Jens Axboe
prev parent reply other threads:[~2014-02-12 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 14:51 [PATCH 0/2] Make fio.h a bit more C++ safe Daniel Gollub
2014-02-12 14:51 ` [PATCH 1/2] Make file.h C++ safe by casting fio_file_flags Daniel Gollub
2014-02-12 14:51 ` [PATCH 2/2] Make parse.h C++ safe by avoiding "or" keyword Daniel Gollub
2014-02-12 15:26 ` Jens Axboe [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=52FB92B6.8070704@kernel.dk \
--to=axboe@kernel.dk \
--cc=d.gollub@telekom.de \
--cc=daniel.gollub@t-online.de \
--cc=fio@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox