From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jan Kara <jack@suse.cz>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
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>
Subject: Re: [GIT PULL] f2fs for 5.14-rc1
Date: Thu, 8 Jul 2021 22:52:21 +1000 [thread overview]
Message-ID: <20210708225221.30f1100b@canb.auug.org.au> (raw)
In-Reply-To: <20210708095217.GA32434@quack2.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
Hi Jan,
On Thu, 8 Jul 2021 11:52:17 +0200 Jan Kara <jack@suse.cz> wrote:
>
> Whether that particular series causing the conflict will be merged by Linus
> in this merge window is uncertain - Linus didn't like how filemap_fault()
> unconditionally acquired the lock. I've created an optimization patch to avoid
> that but review is pending... At this point I'm leaning towards the variant
> that series won't go in during the merge window. In that case I'll
> probably rebase on top of rc1 and force-push everything.
No worries, thanks for the reply.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-08 12:52 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
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 [this message]
2021-07-09 17:41 ` 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=20210708225221.30f1100b@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.