From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>
Cc: Christoph Hellwig <hch@lst•de>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Lu Hongfei <luhongfei@vivo•com>, Yangtao Li <frank.li@vivo•com>
Subject: linux-next: manual merge of the f2fs tree with the mm tree
Date: Fri, 16 Jun 2023 10:25:24 +1000 [thread overview]
Message-ID: <20230616102524.73bb5efb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]
Hi all,
Today's linux-next merge of the f2fs tree got a conflict in:
fs/f2fs/file.c
between commit:
0d625446d0a4 ("backing_dev: remove current->backing_dev_info")
from the mm tree and commit:
d61812691182 ("f2fs: enable nowait async buffered writes")
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/file.c
index 7134fe8bd008,41e7c2b80f31..000000000000
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@@ -4514,12 -4535,12 +4535,9 @@@ static ssize_t f2fs_buffered_write_iter
struct inode *inode = file_inode(file);
ssize_t ret;
- if (iocb->ki_flags & IOCB_NOWAIT)
- return -EOPNOTSUPP;
-
- current->backing_dev_info = inode_to_bdi(inode);
ret = generic_perform_write(iocb, from);
- current->backing_dev_info = NULL;
if (ret > 0) {
- iocb->ki_pos += ret;
f2fs_update_iostat(F2FS_I_SB(inode), inode,
APP_BUFFERED_IO, ret);
}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-06-16 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 0:25 Stephen Rothwell [this message]
2023-06-16 5:52 ` linux-next: manual merge of the f2fs tree with the mm tree Christoph Hellwig
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=20230616102524.73bb5efb@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=frank.li@vivo$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=jaegeuk@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=luhongfei@vivo$(echo .)com \
/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