From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Eric Biggers <ebiggers@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Satya Tangirala <satyat@google.com>, Chao Yu <yuchao0@huawei.com>
Subject: Re: linux-next: manual merge of the f2fs tree with the fscrypt tree
Date: Sun, 9 Aug 2020 18:44:02 +1000 [thread overview]
Message-ID: <20200809184402.20a29137@canb.auug.org.au> (raw)
In-Reply-To: <20200708103858.1196bb65@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]
Hi all,
On Wed, 8 Jul 2020 10:38:58 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the f2fs tree got a conflict in:
>
> Documentation/filesystems/f2fs.rst
>
> between commit:
>
> 38dff4e50c12 ("f2fs: add inline encryption support")
>
> from the fscrypt tree and commit:
>
> a7c77c387b60 ("f2fs: fix to document reserved special compression extension")
>
> 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.
>
> diff --cc Documentation/filesystems/f2fs.rst
> index 8b4fac44f4e1,535021c46260..000000000000
> --- a/Documentation/filesystems/f2fs.rst
> +++ b/Documentation/filesystems/f2fs.rst
> @@@ -258,13 -258,8 +258,15 @@@ compress_extension=%s Support adding s
> on compression extension list and enable compression on
> these file by default rather than to enable it via ioctl.
> For other files, we can still enable compression via ioctl.
> + Note that, there is one reserved special extension '*', it
> + can be set to enable compression for all files.
> +inlinecrypt
> + When possible, encrypt/decrypt the contents of encrypted
> + files using the blk-crypto framework rather than
> + filesystem-layer encryption. This allows the use of
> + inline encryption hardware. The on-disk format is
> + unaffected. For more details, see
> + Documentation/block/inline-encryption.rst.
> ====================== ============================================================
>
> Debugfs Entries
This is now a conflict between the f2fs 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-08-09 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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-05-03 23:40 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=20200809184402.20a29137@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=satyat@google.com \
--cc=tytso@mit.edu \
--cc=yuchao0@huawei.com \
/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).