On Tue, Jul 13, 2021 at 08:14:04PM +0000, Al Viro wrote: > On Tue, Jul 13, 2021 at 12:15:13PM -0700, Linus Torvalds wrote: > > On Tue, Jul 13, 2021 at 3:45 AM Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > > > > > > Linus, sorry for sending this directly through you, instead of going > > > through some other tree, but trying to get this upstream through the > > > linux-fsdevel list / patch-review simply is not working. > > > > Well, the filesystem maintainer sending their patches to me as a pull > > request is actually the norm rather than the exception when it comes > > to filesystems. > > > > It's a bit different for drivers, but that's because while we have > > multiple filesystems, we have multiple _thousand_ drivers, so on the > > driver side I really don't want individual driver maintainers to all > > send me their individual pull requests - that just wouldn't scale. > > > > So for individual drivers, we have subsystem maintainers, but for > > individual filesystems we generally don't. > > > > (When something then touches the *common* vfs code, that's a different > > thing - but something like this vboxsf thing this pull request looks > > normal to me). > > To elaborate a bit - there's one case when I want it to go through > vfs.git, and that's when there's an interference between something > going on in vfs.git and the work done in filesystem. Example: if there's a series changing calling conventions for some method brewing in vfs.git and changes to filesystem's instance of that method in the filesystem tree. Then I'd rather it coordinated before either gets merged. It might be an invariant branch in either tree pulled by both, it might be a straight pull into vfs.git and sorting the things out there - depends upon the situation.
