From: David Chinner <dgc@sgi.com>
To: Manoj Kumar Pradhan <manojkp80@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Deviation from XSDM in DM_EVENT_XXX
Date: Wed, 7 Nov 2007 20:55:30 +1100 [thread overview]
Message-ID: <20071107095530.GJ995458@sgi.com> (raw)
In-Reply-To: <cce360c30711062032w11ec966fy52f4702c2fff61db@mail.gmail.com>
On Wed, Nov 07, 2007 at 10:02:12AM +0530, Manoj Kumar Pradhan wrote:
> Hi,
>
> Can someone tell me why XFS-DMAPI deviates in the enum DM_EVEN_XXX
> from the standard?
>From the spec:
(http://www.opengroup.org/onlinepubs/9657099/chap4.htm)
"
dm_eventtype_t
REQUIREMENT
This enumeration must contain at least the elements listed here. The DMAPI
implementation may choose a different order for the elements.
"
So as long as we have the events defined, it doesn't matter what
their value or order in the enum is. It's a very rubbery spec....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2007-11-07 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 4:32 Deviation from XSDM in DM_EVENT_XXX Manoj Kumar Pradhan
2007-11-07 9:55 ` David Chinner [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=20071107095530.GJ995458@sgi.com \
--to=dgc@sgi.com \
--cc=manojkp80@gmail.com \
--cc=xfs@oss.sgi.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