| Message ID | 20240405121332.689228-1-eugen.hristev@collabora.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Cache insensitive cleanup for ext4/f2fs | expand |
On Fri, Apr 05, 2024 at 03:13:23PM +0300, Eugen Hristev wrote: > Hello, > > I am trying to respin the series here : > https://www.spinics.net/lists/linux-ext4/msg85081.html The subject here is "Cache insensitive cleanup for ext4/f2fs". Cache insensitive means something entirely different https://en.wikipedia.org/wiki/Cache-oblivious_algorithm I suspect you mean "Case insensitive".
On 4/5/24 15:18, Matthew Wilcox wrote: > On Fri, Apr 05, 2024 at 03:13:23PM +0300, Eugen Hristev wrote: >> Hello, >> >> I am trying to respin the series here : >> https://www.spinics.net/lists/linux-ext4/msg85081.html > > The subject here is "Cache insensitive cleanup for ext4/f2fs". > Cache insensitive means something entirely different > https://en.wikipedia.org/wiki/Cache-oblivious_algorithm > > I suspect you mean "Case insensitive". You are correct, I apologize for the typo. > _______________________________________________ > Kernel mailing list -- kernel@mailman.collabora.com > To unsubscribe send an email to kernel-leave@mailman.collabora.com > This list is managed by https://mailman.collabora.com
Eugen Hristev <eugen.hristev@collabora.com> writes: > On 4/5/24 15:18, Matthew Wilcox wrote: >> On Fri, Apr 05, 2024 at 03:13:23PM +0300, Eugen Hristev wrote: >>> Hello, >>> >>> I am trying to respin the series here : >>> https://www.spinics.net/lists/linux-ext4/msg85081.html >> >> The subject here is "Cache insensitive cleanup for ext4/f2fs". >> Cache insensitive means something entirely different >> https://en.wikipedia.org/wiki/Cache-oblivious_algorithm >> >> I suspect you mean "Case insensitive". > > You are correct, I apologize for the typo. Heh. I completely missed it in the previous submissions. I guess we both just mentally auto-corrected. Since we are here, I think I contributed to the typo in the cover letter with the summary lines of patch 1 and 2. Differently from the rest of the series, these two are actually working on a "cache of casefolded strings". But their summary lines are misleading. Can you rename them to: [PATCH v16 1/9] ext4: Simplify the handling of cached casefolded names [PATCH v16 2/9] f2fs: Simplify the handling of cached casefolded names From a quick look, the series is looking good and the strict mode issue pointed in the last iteration seems fixed, though I didn't run it yet. I'll take a closer look later today and fully review.
Hello Krisman, On 4/5/24 19:37, Gabriel Krisman Bertazi wrote: > Eugen Hristev <eugen.hristev@collabora.com> writes: > >> On 4/5/24 15:18, Matthew Wilcox wrote: >>> On Fri, Apr 05, 2024 at 03:13:23PM +0300, Eugen Hristev wrote: >>>> Hello, >>>> >>>> I am trying to respin the series here : >>>> https://www.spinics.net/lists/linux-ext4/msg85081.html >>> >>> The subject here is "Cache insensitive cleanup for ext4/f2fs". >>> Cache insensitive means something entirely different >>> https://en.wikipedia.org/wiki/Cache-oblivious_algorithm >>> >>> I suspect you mean "Case insensitive". >> >> You are correct, I apologize for the typo. > > Heh. I completely missed it in the previous submissions. I guess we both > just mentally auto-corrected. > > Since we are here, I think I contributed to the typo in the cover letter > with the summary lines of patch 1 and 2. Differently from the rest of > the series, these two are actually working on a "cache of > casefolded strings". But their summary lines are misleading. > > Can you rename them to: > > [PATCH v16 1/9] ext4: Simplify the handling of cached casefolded names > [PATCH v16 2/9] f2fs: Simplify the handling of cached casefolded names > > From a quick look, the series is looking good and the strict mode issue > pointed in the last iteration seems fixed, though I didn't run it yet. > I'll take a closer look later today and fully review. > Have you managed to take a look ? What would be the future of the series ? I didn't want to send another version for just a subject change, but I can if that's the only change required . Thanks, Eugen
Hello: This series was applied to jaegeuk/f2fs.git (dev) by Christian Brauner <brauner@kernel.org>: On Fri, 5 Apr 2024 15:13:23 +0300 you wrote: > Hello, > > I am trying to respin the series here : > https://www.spinics.net/lists/linux-ext4/msg85081.html > > I resent some of the v9 patches and got some reviews from Gabriel, > I did changes as requested and here is v16. > > [...] Here is the summary with links: - [f2fs-dev,v16,1/9] ext4: Simplify the handling of cached insensitive names https://git.kernel.org/jaegeuk/f2fs/c/f776f02a2c96 - [f2fs-dev,v16,2/9] f2fs: Simplify the handling of cached insensitive names https://git.kernel.org/jaegeuk/f2fs/c/632f4054b229 - [f2fs-dev,v16,3/9] libfs: Introduce case-insensitive string comparison helper (no matching commit) - [f2fs-dev,v16,4/9] ext4: Reuse generic_ci_match for ci comparisons (no matching commit) - [f2fs-dev,v16,5/9] f2fs: Reuse generic_ci_match for ci comparisons https://git.kernel.org/jaegeuk/f2fs/c/d66858eb0c72 - [f2fs-dev,v16,6/9] ext4: Log error when lookup of encoded dentry fails (no matching commit) - [f2fs-dev,v16,7/9] f2fs: Log error when lookup of encoded dentry fails (no matching commit) - [f2fs-dev,v16,8/9] ext4: Move CONFIG_UNICODE defguards into the code flow https://git.kernel.org/jaegeuk/f2fs/c/d98c822232f8 - [f2fs-dev,v16,9/9] f2fs: Move CONFIG_UNICODE defguards into the code flow https://git.kernel.org/jaegeuk/f2fs/c/28add38d545f You are awesome, thank you!