From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well
Date: Wed, 22 Apr 2020 15:26:12 +0000 [thread overview]
Message-ID: <bug-206057-202145-E4C8t4f7B6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206057-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206057
Balazs Vinarz (vinibali1@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vinibali1@gmail.com
--- Comment #8 from Balazs Vinarz (vinibali1@gmail.com) ---
Hello there,
as a 32bit ARM user, I'm also affected.
Will this fix be in 5.7?
Regards
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-04-22 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 23:32 [f2fs-dev] [Bug 206057] New: 5.5.0: f2fs is extremely slow, with ext4 system works well bugzilla-daemon
2020-01-01 23:33 ` [f2fs-dev] [Bug 206057] 5.5.0-rc2-next: " bugzilla-daemon
2020-01-02 2:01 ` bugzilla-daemon
2020-01-02 10:40 ` bugzilla-daemon
2020-01-02 20:34 ` bugzilla-daemon
2020-01-03 7:27 ` bugzilla-daemon
2020-01-03 15:47 ` bugzilla-daemon
2020-02-29 8:37 ` bugzilla-daemon
2020-03-24 8:25 ` bugzilla-daemon
2020-04-22 15:26 ` bugzilla-daemon [this message]
2020-04-22 16:38 ` bugzilla-daemon
2021-08-11 6:19 ` bugzilla-daemon
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=bug-206057-202145-E4C8t4f7B6@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).