From: Robin Hsu <robinh3123@gmail.com> To: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org, chao@kernel.org Cc: linux-kernel@vger.kernel.org, Robin Hsu <robinhsu@google.com> Subject: Please ignore "sload compression support" patches without "v3" Date: Tue, 8 Dec 2020 16:26:05 +0800 [thread overview] Message-ID: <20201208082605.654422-1-robinh3123@gmail.com> (raw) From: Robin Hsu <robinhsu@google.com> Hi, All, Due to my mistakes, patches for sload compression support were sent without "v3" (version 3). That was corrected by resending them again, with the correct subject (with "v3"). Please ignore those emails without "v3". I apologize for the inconvenience. Best regards, Robin Hsu
WARNING: multiple messages have this Message-ID (diff)
From: Robin Hsu <robinh3123@gmail.com> To: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org, chao@kernel.org Cc: linux-kernel@vger.kernel.org Subject: [f2fs-dev] Please ignore "sload compression support" patches without "v3" Date: Tue, 8 Dec 2020 16:26:05 +0800 [thread overview] Message-ID: <20201208082605.654422-1-robinh3123@gmail.com> (raw) From: Robin Hsu <robinhsu@google.com> Hi, All, Due to my mistakes, patches for sload compression support were sent without "v3" (version 3). That was corrected by resending them again, with the correct subject (with "v3"). Please ignore those emails without "v3". I apologize for the inconvenience. Best regards, Robin Hsu _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2020-12-08 8:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-08 8:26 Robin Hsu [this message] 2020-12-08 8:26 ` [f2fs-dev] Please ignore "sload compression support" patches without "v3" Robin Hsu
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=20201208082605.654422-1-robinh3123@gmail.com \ --to=robinh3123@gmail.com \ --cc=chao@kernel.org \ --cc=jaegeuk@kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-kernel@vger.kernel.org \ --cc=robinhsu@google.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: linkBe 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.