From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>, Jan Kara <jack@suse.cz>
Subject: Re: [GIT PULL] f2fs for 5.14-rc1
Date: Thu, 8 Jul 2021 09:46:47 +1000 [thread overview]
Message-ID: <20210708094647.7c0d3060@canb.auug.org.au> (raw)
In-Reply-To: <YOYHejl3CgABOnhP@google.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Hi Jaegeuk,
On Wed, 7 Jul 2021 12:58:50 -0700 Jaegeuk Kim <jaegeuk@kernel.org> wrote:
>
> Could you please consider this pull request?
>
> Thanks,
>
> The following changes since commit bd3c9cdb21a2674dd0db70199df884828e37abd4:
>
> Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2021-05-14 10:52:47 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-5.14-rc1
>
> for you to fetch changes up to 28607bf3aa6f9762b32dc7f1ed0488823c0651b8:
>
> f2fs: drop dirty node pages when cp is in error status (2021-07-06 22:05:06 -0700)
Its worth mentioning the semantic conflict against the ext3 tree (which
hasn't been merged by Linus yet, but presumably will be).
https://lore.kernel.org/lkml/20210623104922.30a5a3fa@canb.auug.org.au/
The ext3 commit has been rebased and is now
1474c39351f0 ("f2fs: Convert to using invalidate_lock")
but I am still applying the mentioned merge resolution patch.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-07 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 19:58 [GIT PULL] f2fs for 5.14-rc1 Jaegeuk Kim
2021-07-07 19:58 ` [f2fs-dev] " Jaegeuk Kim
2021-07-07 23:46 ` Stephen Rothwell [this message]
2021-07-08 0:10 ` Jaegeuk Kim
2021-07-08 0:10 ` [f2fs-dev] " Jaegeuk Kim
2021-07-08 9:52 ` Jan Kara
2021-07-08 9:52 ` [f2fs-dev] " Jan Kara
2021-07-08 12:52 ` Stephen Rothwell
2021-07-09 17:41 ` [f2fs-dev] " pr-tracker-bot
2021-07-09 17:41 ` pr-tracker-bot
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=20210708094647.7c0d3060@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.