From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-fsdevel@vger.kernel.org, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>,
ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 12/44] docs: filesystems: convert dlmfs.txt to ReST
Date: Tue, 18 Feb 2020 11:07:31 +0100 [thread overview]
Message-ID: <20200218110731.2890658d@kernel.org> (raw)
In-Reply-To: <3b40d7d4-3798-08db-220d-b45704ada48a@linux.alibaba.com>
Em Tue, 18 Feb 2020 09:21:51 +0800
Joseph Qi <joseph.qi@linux.alibaba.com> escreveu:
> On 20/2/18 00:11, Mauro Carvalho Chehab wrote:
> > @@ -96,14 +101,19 @@ operation. If the lock succeeds, you'll get an fd.
> > open(2) with O_CREAT to ensure the resource inode is created - dlmfs does
> > not automatically create inodes for existing lock resources.
> >
> > +============ ===========================
> > Open Flag Lock Request Type
> > ---------- -----------------
>
> Better to remove the above line.
>
> > +============ ===========================
> > O_RDONLY Shared Read
> > O_RDWR Exclusive
> > +============ ===========================
> >
> > +
> > +============ ===========================
> > Open Flag Resulting Locking Behavior
> > ---------- --------------------------
>
> Ditto.
Ok. So, I guess we can just merge the two tables into one, like:
============ =================
O_RDONLY Shared Read
O_RDWR Exclusive
O_NONBLOCK Trylock operation
============ =================
Right?
Cheers,
Mauro
next prev parent reply other threads:[~2020-02-18 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:11 [Ocfs2-devel] [PATCH 00/44] Manually convert filesystem FS documents to ReST Mauro Carvalho Chehab
2020-02-17 16:11 ` [Ocfs2-devel] [PATCH 12/44] docs: filesystems: convert dlmfs.txt " Mauro Carvalho Chehab
2020-02-18 1:21 ` Joseph Qi
2020-02-18 10:07 ` Mauro Carvalho Chehab [this message]
2020-02-18 10:55 ` Joseph Qi
2020-02-17 16:12 ` [Ocfs2-devel] [PATCH 29/44] docs: filesystems: convert ocfs2.txt " Mauro Carvalho Chehab
2020-02-18 1:23 ` Joseph Qi
2020-02-18 4:01 ` [Ocfs2-devel] [PATCH 00/44] Manually convert filesystem FS documents " Matthew Wilcox
2020-02-18 10:04 ` Mauro Carvalho Chehab
2020-02-19 9:32 ` Jonathan Corbet
2020-02-19 15:11 ` Mauro Carvalho Chehab
2020-03-02 21:13 ` Jonathan Corbet
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=20200218110731.2890658d@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.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