On 7/13/21 1:18 PM, Al Viro wrote: > 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: >>>> ... >>> >>> (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. > Hi Al, Where would you prefer for kernel-doc changes in fs/*.[ch] be merged? E.g., from June 27: https://lore.kernel.org/linux-fsdevel/20210628014613.11296-1-rdunlap@xxxxxxxxxxxxx/ thanks. -- ~Randy
