On Sat, 25 Jan 2025, Matthew Wilcox wrote: > > Ultimately, I think you'll want to describe the workflow you see Lustre > adopting once it's upstream -- I've had too many filesystems say to me > "Oh, you have to submit your patch against our git tree and then we'll > apply it to the kernel later". That's not acceptable; the kernel is > upstream, not your private git tree. > > While I generally agree with your sentiment, I think there is more nuance in the details than you portray. With nfsd, for example, I can sometimes submit patches against mainline but sometimes need to submit against nfsd-next or even nfsd-testing if someone else has been working in the same area. And it may well be a couple of releases "later" that it lands in Linus' kernel - though that isn't the norm. But certainly we need to be clear about the workflow - not least within the lustre community who are used to a very different work-flow and will need to learn. Thanks, NeilBrown
