From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 218770] fsck seems unable to solve corruption
Date: Tue, 14 May 2024 16:32:04 +0000 [thread overview]
Message-ID: <bug-218770-202145-kwKRxyQK1E@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218770-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218770
--- Comment #9 from Jaegeuk Kim (jaegeuk@kernel.org) ---
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=b864ddb57eb00c4ea1e6801c7b2f70f1db2a7f4b
is going to be merged in upcoming weeks and LTS probably will pick up later
given the tag.
--
You may reply to this email to add a comment.
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:[~2024-05-14 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 11:40 [f2fs-dev] [Bug 218770] New: fsck seems unable to solve corruption bugzilla-daemon
2024-04-24 11:41 ` [f2fs-dev] [Bug 218770] " bugzilla-daemon
2024-04-24 12:19 ` bugzilla-daemon
2024-04-24 12:22 ` bugzilla-daemon
2024-04-24 12:25 ` bugzilla-daemon
2024-04-24 12:30 ` bugzilla-daemon
2024-04-24 12:40 ` Tor Vic via Linux-f2fs-devel
[not found] ` <CAL0yVhy5zW1wUAsN1+the3UnkG0cy84B9nXEWUZDOVN=Q2+tDw@mail.gmail.com>
2024-04-24 12:47 ` Tor Vic via Linux-f2fs-devel
2024-04-24 17:30 ` bugzilla-daemon
2024-04-29 15:58 ` bugzilla-daemon
2024-05-14 11:41 ` bugzilla-daemon
2024-05-14 16:32 ` bugzilla-daemon [this message]
2024-05-17 20:02 ` bugzilla-daemon
2024-05-20 20:08 ` bugzilla-daemon
2024-05-20 21:42 ` bugzilla-daemon
2024-05-25 19:45 ` bugzilla-daemon
2024-05-25 19:46 ` bugzilla-daemon
2024-05-28 16:56 ` 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-218770-202145-kwKRxyQK1E@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 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.