[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SA1PR11MB673492082606C66ED2F0717EA85CA@SA1PR11MB6734.namprd11.prod.outlook.com>
Date: Tue, 20 Jun 2023 00:04:08 +0000
From: "Li, Xin3" <xin3.li@...el.com>
To: "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
CC: "mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"andrew.cooper3@...rix.com" <andrew.cooper3@...rix.com>,
"Christopherson,, Sean" <seanjc@...gle.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>,
"jiangshanlai@...il.com" <jiangshanlai@...il.com>,
"Kang, Shan" <shan.kang@...el.com>
Subject: RE: [PATCH v8 01/33] x86/traps: let common_interrupt() handle
IRQ_MOVE_CLEANUP_VECTOR
> >Okay, it's a bit wired to me to rename before any actual code logic change.
> >
>
> Weird or not, that's the established practice.
>
> However, if you think about it, it makes sense: that way your code logic patch
> doesn't contain a bunch of names which will almost immediately be outdated. That
> is *really* confusing when you are going back through the git history, for example.
Thanks for the clarification!
Xin
Powered by blists - more mailing lists