Dave Hansen <dave.hansen@xxxxxxxxx> writes: > On 3/15/23 14:15, Jonathan Corbet wrote: >> On the other hand, it *is* a fair amount of churn. If it's more than >> people can handle, I'll quietly back away and we'll muddle along as we have >> been; this isn't something I'm going to dig in my heels over. > > I'm not fundamentally opposed to this. It'll probably cost me a few > keystrokes in moments of confusion, but that's the price of progress. :) > > Things in Documentation/ have also been mobile enough in recent years > that I tend to "find Documentation | grep something" rather than try to > remember the paths for things. Adding an arch/ in there won't hurt > anything. So, if I'm not going to get tarred and feathered for this, I'd like to proceed, and am wondering what the best way is. Patch 1 is a pure docs change that won't affect anybody. I could also apply #2 if I could get an ack from the x86 community, but that is sure to create conflicts with tip and get us all more cheery notes from Stephen Rothwell. I could do the "fix up and send at the end of the merge window" trick with it. Or perhaps some of this should go via tip? Suggestions welcome. Thanks, jon
