Re: [f2fs-dev] [GIT PULL] zstd changes for v5.16

2021-11-11 Thread Nick Terrell via Linux-f2fs-devel
> On Nov 11, 2021, at 2:59 PM, Linus Torvalds > wrote: > > On Wed, Nov 10, 2021 at 10:47 AM Nick Terrell wrote: >> >> I just wanted to make sure that you’ve received my pull request. I’m a newbie >> here, so I want to make sure I’m not making a stupid mistake that means >> you’ve >> missed

Re: [f2fs-dev] [GIT PULL] zstd changes for v5.16

2021-11-11 Thread Linus Torvalds
On Wed, Nov 10, 2021 at 10:47 AM Nick Terrell wrote: > > I just wanted to make sure that you’ve received my pull request. I’m a newbie > here, so I want to make sure I’m not making a stupid mistake that means you’ve > missed my message. I’d hate for this PR to not even be considered for merging >

Re: [f2fs-dev] [GIT PULL] zstd changes for v5.16

2021-11-11 Thread Nick Terrell via Linux-f2fs-devel
> On Nov 8, 2021, at 5:30 PM, Nick Terrell wrote: > > From: Nick Terrell > > Hi Linus, > > I am sending you a pull request to add myself as the maintainer of zstd and > update the zstd version in the kernel, which is now 4 years out of date, > to the latest zstd release. This includes bug

Re: [f2fs-dev] [GIT PULL] f2fs update for 5.16-rc1

2021-11-11 Thread Jaegeuk Kim
On 11/11, Christoph Hellwig wrote: > So question on the direct I/O code. The perfectly fine iomap code > wasn't merged because of the pre-existing stale data exposure issuewith > f2fs direct I/O low-level implementation. This doesn't seem to be fixed > or even worked around, but instead we do

Re: [f2fs-dev] [GIT PULL] f2fs update for 5.16-rc1

2021-11-11 Thread Christoph Hellwig
So question on the direct I/O code. The perfectly fine iomap code wasn't merged because of the pre-existing stale data exposure issuewith f2fs direct I/O low-level implementation. This doesn't seem to be fixed or even worked around, but instead we do get new direct I/O features? On Wed, Nov 10,