From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dominique Martinet <asmadeus@codewreck•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel•org>,
Jonathan Corbet <corbet@lwn•net>
Subject: linux-next: manual merge of the v9fs tree with Linus' tree
Date: Thu, 9 Apr 2020 11:03:20 +1000 [thread overview]
Message-ID: <20200409110320.3de95e0b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
Hi all,
Today's linux-next merge of the v9fs tree got a conflict in:
Documentation/filesystems/9p.rst
between commit:
07d241fd66ba ("docs: filesystems: convert 9p.txt to ReST")
from Linus' tree and commit:
c6f141412d24 ("9p: document short read behaviour with O_NONBLOCK")
from the v9fs tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc Documentation/filesystems/9p.rst
index f054d1c45e86,3fb780ffdf23..000000000000
--- a/Documentation/filesystems/9p.rst
+++ b/Documentation/filesystems/9p.rst
@@@ -156,9 -132,18 +156,19 @@@ Option
cachetag cache tag to use the specified persistent cache.
cache tags for existing cache sessions can be listed at
/sys/fs/9p/caches. (applies only to cache=fscache)
+ ============= ===============================================================
-BEHAVIOR
++Behavior
+ ========
+
+ This section aims at describing 9p 'quirks' that can be different
+ from a local filesystem behaviors.
+
+ - Setting O_NONBLOCK on a file will make client reads return as early
+ as the server returns some data instead of trying to fill the read
+ buffer with the requested amount of bytes or end of file is reached.
+
-RESOURCES
+Resources
=========
Protocol specifications are maintained on github:
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-09 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 1:03 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-29 1:21 linux-next: manual merge of the v9fs tree with Linus' tree Stephen Rothwell
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=20200409110320.3de95e0b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=asmadeus@codewreck$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab+huawei@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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