linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Theodore Ts'o <tytso@mit.edu>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tomohiro Kusumi <tkusumi@tuxera.com>
Subject: linux-next: manual merge of the f2fs tree with the fscrypt tree
Date: Thu, 4 May 2017 09:40:40 +1000	[thread overview]
Message-ID: <20170504094040.56b36c73@canb.auug.org.au> (raw)

Hi Jaegeuk,

Today's linux-next merge of the f2fs tree got a conflict in:

  fs/f2fs/inline.c

between commit:

  5fc36386d220 ("f2fs: check entire encrypted bigname when finding a dentry")

from the fscrypt tree and commit:

  64c24ecb3cff ("f2fs: split make_dentry_ptr() into block and inline versions")

from the f2fs 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 fs/f2fs/inline.c
index fa729ff6b2f9,0ccdefe9fdba..000000000000
--- a/fs/f2fs/inline.c
+++ b/fs/f2fs/inline.c
@@@ -533,8 -533,8 +533,8 @@@ int f2fs_add_inline_entry(struct inode 
  
  	f2fs_wait_on_page_writeback(ipage, NODE, true);
  
 -	name_hash = f2fs_dentry_hash(new_name);
 +	name_hash = f2fs_dentry_hash(new_name, NULL);
- 	make_dentry_ptr(NULL, &d, (void *)dentry_blk, 2);
+ 	make_dentry_ptr_inline(NULL, &d, dentry_blk);
  	f2fs_update_dentry(ino, mode, &d, new_name, name_hash, bit_pos);
  
  	set_page_dirty(ipage);

             reply	other threads:[~2017-05-03 23:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 23:40 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-08  0:38 linux-next: manual merge of the f2fs tree with the fscrypt tree Stephen Rothwell
2020-08-09  8:44 ` Stephen Rothwell
2020-05-21  0:30 Stephen Rothwell
2018-12-10 23:13 Stephen Rothwell
2019-01-02  0:26 ` Stephen Rothwell
2019-01-02  4:56   ` Chandan Rajendra
2018-01-14 22:17 Stephen Rothwell
2017-02-14 22:51 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=20170504094040.56b36c73@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jaegeuk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tkusumi@tuxera.com \
    --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).