linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-xfs@vger.kernel.org,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: manual merge of the xfs tree with Linus' tree
Date: Wed, 31 Oct 2018 12:05:57 +1100	[thread overview]
Message-ID: <20181031010557.GU19305@dastard> (raw)
In-Reply-To: <20181031112244.71b62e67@canb.auug.org.au>

On Wed, Oct 31, 2018 at 11:22:44AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the xfs tree got a conflict in:
> 
>   Documentation/filesystems/porting
> 
> between commit:
> 
>   1a16dbaf798c ("Document d_splice_alias() calling conventions for ->lookup() users.")
> 
> from Linus' tree and commit:
> 
>   2e5dfc99f2e6 ("vfs: combine the clone and dedupe into a single remap_file_range")
> 
> from the xfs 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/porting
> index 321d74b73937,e6d4466268dd..000000000000
> --- a/Documentation/filesystems/porting
> +++ b/Documentation/filesystems/porting
> @@@ -623,13 -623,7 +623,18 @@@ in your dentry operations instead
>   	On success you get a new struct file sharing the mount/dentry with the
>   	original, on failure - ERR_PTR().
>   --
>  +[recommended]
>  +	->lookup() instances doing an equivalent of
>  +		if (IS_ERR(inode))
>  +			return ERR_CAST(inode);
>  +		return d_splice_alias(inode, dentry);
>  +	don't need to bother with the check - d_splice_alias() will do the
>  +	right thing when given ERR_PTR(...) as inode.  Moreover, passing NULL
>  +	inode to d_splice_alias() will also do the right thing (equivalent of
>  +	d_add(dentry, NULL); return NULL;), so that kind of special cases
>  +	also doesn't need a separate treatment.
> ++--
> + [mandatory]
> + 	->clone_file_range() and ->dedupe_file_range have been replaced with
> + 	->remap_file_range().  See Documentation/filesystems/vfs.txt for more
> + 	information.

Looks good - I knew about this one from merging back into a recent
Linus kernel.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2018-10-31  1:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  0:22 linux-next: manual merge of the xfs tree with Linus' tree Stephen Rothwell
2018-10-31  1:05 ` Dave Chinner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-31  0:41 Stephen Rothwell
2022-03-30 22:00 Stephen Rothwell
2022-01-17 22:30 Stephen Rothwell
2022-01-18 18:17 ` Darrick J. Wong
2019-07-16 23:36 Stephen Rothwell
2018-06-05  0:34 Stephen Rothwell
2018-06-05  0:38 ` Stephen Rothwell
2018-06-05  0:59 ` Dave Chinner
2018-06-05  1:13   ` Andreas Grünbacher
2018-06-05  1:25   ` Stephen Rothwell
2017-12-21 22:50 Stephen Rothwell
2017-12-21 23:01 ` Darrick J. Wong
2016-07-21  1:07 Stephen Rothwell
2016-07-21  1:35 ` Dave Chinner
2015-04-20  2:24 Stephen Rothwell
2012-01-03  1:06 Stephen Rothwell
2012-01-03  1:34 ` Dave Chinner
2011-09-15  2:30 Stephen Rothwell
2011-09-15 11:05 ` Christoph Hellwig
2011-03-28  1:21 Stephen Rothwell
2009-08-18  0:12 Stephen Rothwell
2009-08-18  6:49 ` Felix Blyakher
2009-08-18  7:17   ` 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=20181031010557.GU19305@dastard \
    --to=david@fromorbit.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    /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).