[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y2jw4ne6.fsf@nanos.tec.linutronix.de>
Date: Fri, 23 Oct 2020 23:56:33 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: ira.weiny@...el.com, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Cc: Ira Weiny <ira.weiny@...el.com>, x86@...nel.org,
Dave Hansen <dave.hansen@...ux.intel.com>,
Dan Williams <dan.j.williams@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Fenghua Yu <fenghua.yu@...el.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-nvdimm@...ts.01.org,
linux-mm@...ck.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 07/10] x86/entry: Pass irqentry_state_t by reference
On Thu, Oct 22 2020 at 15:26, ira weiny wrote:
> From: Ira Weiny <ira.weiny@...el.com>
>
> In preparation for adding PKS information to struct irqentry_state_t
> change all call sites and usages to pass the struct by reference
> instead of by value.
This still does not explain WHY you need to do that. 'Preparation' is a
pretty useless information.
What is the actual reason for this? Just because PKS information feels
better that way?
Also what is PKS information? Changelogs have to make sense on their own
and not only in the context of a larger series of changes.
> While we are editing the call sites it is a good time to standardize on
> the name 'irq_state'.
While at it change all usage sites to consistently use the variable
name 'irq_state'.
Or something like that. See Documentation/process/...
Thanks,
tglx
Powered by blists - more mailing lists