From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jonathan Corbet <corbet@lwn.net>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: manual merge of the jc_docs tree with the ext4 tree
Date: Wed, 3 Jun 2020 12:27:50 +1000 [thread overview]
Message-ID: <20200603122750.70bf9c55@canb.auug.org.au> (raw)
In-Reply-To: <20200522130616.5fd7054c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
Hi all,
On Fri, 22 May 2020 13:06:16 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the jc_docs tree got a conflict in:
>
> Documentation/filesystems/fiemap.rst
>
> between commit:
>
> 469581d9e5c9 ("fs: move fiemap range validation into the file systems instances")
>
> from the ext4 tree and commit:
>
> e6f7df74ec1a ("docs: filesystems: convert fiemap.txt to ReST")
>
> from the jc_docs tree.
>
> diff --cc Documentation/filesystems/fiemap.rst
> index 35c8571eccb6,2a572e7edc08..000000000000
> --- a/Documentation/filesystems/fiemap.rst
> +++ b/Documentation/filesystems/fiemap.rst
> @@@ -203,10 -206,9 +206,10 @@@ EINTR once fatal signal received
>
>
> Flag checking should be done at the beginning of the ->fiemap callback via the
> - fiemap_prep() helper:
> -fiemap_check_flags() helper::
> ++fiemap_prep() helper::
>
> - int fiemap_prep(struct inode *inode, struct fiemap_extent_info *fieinfo,
> - u64 start, u64 *len, u32 supported_flags);
> - int fiemap_check_flags(struct fiemap_extent_info *fieinfo, u32 fs_flags);
> ++ int fiemap_prep(struct inode *inode, struct fiemap_extent_info *fieinfo,
> ++ u64 start, u64 *len, u32 supported_flags);
>
> The struct fieinfo should be passed in as received from ioctl_fiemap(). The
> set of fiemap flags which the fs understands should be passed via fs_flags. If
This is now a conflict between the ext4 tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-03 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 3:06 linux-next: manual merge of the jc_docs tree with the ext4 tree Stephen Rothwell
2020-06-03 2:27 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-02 1:15 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=20200603122750.70bf9c55@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).