From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] syscalls/fallocate04: add new fallocate() test
Date: Mon, 13 Apr 2015 17:16:58 +0300 [thread overview]
Message-ID: <552BCFDA.40301@oracle.com> (raw)
In-Reply-To: <552BC7C7.1010105@oracle.com>
On 04/13/2015 04:42 PM, Alexey Kodanev wrote:
> Hi!
> On 04/13/2015 05:33 AM, Xiaoguang Wang wrote:
>>> +
>>> +#define SEEK_HOLE 4
>>> +#define FALLOC_FL_KEEP_SIZE 0x01
>>> +#define FALLOC_FL_PUNCH_HOLE 0x02
>>> +#define FALLOC_FL_COLLAPSE_RANGE 0x08
>>> +#define FALLOC_FL_ZERO_RANGE 0x10
>> What about something like this:
>> #ifndef FALLOC_FL_KEEP_SIZE 4
>> #define FALLOC_FL_KEEP_SIZE 4
>> #endif
>> In case, glibc have already defines these macro now or in future.
> Redefinition with the same values doesn't produce any warnings, but on
> the other hand what if we want to know when they are different?
In case glibc defines them as '1', etc. it will produce a warning, so
it's better take your advice.
Best regards,
Alexey
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2015-04-13 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 13:32 [LTP] [PATCH] syscalls/fallocate04: add new fallocate() test Alexey Kodanev
2015-04-13 2:33 ` Xiaoguang Wang
2015-04-13 13:42 ` Alexey Kodanev
2015-04-13 14:16 ` Alexey Kodanev [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=552BCFDA.40301@oracle.com \
--to=alexey.kodanev@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vasily.isaenko@oracle.com \
--cc=wangxg.fnst@cn.fujitsu.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