On Wed, Feb 07, 2024, Paul Durrant wrote: > On 07/02/2024 04:14, Sean Christopherson wrote: > > Please stop making up random scopes. Yes, I know "KVM: selftests:" is too coarse, > > bt everyone doing their own thing is worse. > > So what would you suggest? Until someone comes up with a better idea that at least a majority of developers agree on, maintain the status quo and use "KVM: selftests:" for the scope, and call out and/or allude to the relevant test(s) in the shortlog. E.g. you can even squeeze in both: KVM: selftests: Map Xen's shared_info page by HVA, not GPA in xen_shinfo_test I know it's kludgy and silly, but it's consistent. Aside from consistency, the "problem" with selftests is that most changes are either specific to one test, or affect multiple tests that have no common denominator beyond KVM. And for changes that are targeted at a single test, I find it helpful if the shortlog specifies the exact test that's being changed. To be clear, I am definitely open to ideas if people feel "KVM: selftests" isn't working, I just want us to make a decision as a group and commit to it, as opposed to people using whatever scope suits their fancy.
