Displaying 3 results from an estimated 3 matches for "minix_renam".
Did you mean:
minix_rename
2023 Jan 18
1
remove most callers of write_one_page v3
...ches)
> > - fix the existing minix code to properly propagate errors
>
> Grabbed. I'll split that into per-fs branches (and synchronize wrt
> fixes), fold the kmap_local stuff into that and push out.
BTW, do you have the check for minix_delete_entry() failure when called
from minix_rename() anywhere in your tree? I don't see that in this
series; I'm adding the trivial fix, hopefully that won't end up
creating conflicts...
2023 Jan 18
9
remove most callers of write_one_page v3
Hi all,
this series removes most users of the write_one_page API. These helpers
internally call ->writepage which we are gradually removing from the
kernel.
Changes since v2:
- more minix error handling fixes
Changes since v1:
- drop the btrfs changes (queue up in the btrfs tree)
- drop the finaly move to jfs (can't be done without the btrfs patches)
- fix the existing minix code to
2023 Jan 18
1
remove most callers of write_one_page v3
On Wed, Jan 18, 2023 at 06:30:20PM +0100, Christoph Hellwig wrote:
> Hi all,
>
> this series removes most users of the write_one_page API. These helpers
> internally call ->writepage which we are gradually removing from the
> kernel.
>
> Changes since v2:
> - more minix error handling fixes
>
> Changes since v1:
> - drop the btrfs changes (queue up in the