[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad071c01174bfb76ec790a2b43db2892e5b652e9.camel@gmail.com>
Date: Fri, 11 Mar 2022 09:33:20 +0200
From: Artem Bityutskiy <dedekind1@...il.com>
To: "Chang S. Bae" <chang.seok.bae@...el.com>,
"Rafael J. Wysocki" <rafael@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
the arch/x86 maintainers <x86@...nel.org>,
Linux PM <linux-pm@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>,
"Ravi V. Shankar" <ravi.v.shankar@...el.com>
Subject: Re: [PATCH v2 2/2] intel_idle: Add a new flag to initialize the AMX
state
On Thu, 2022-03-10 at 10:50 -0800, Chang S. Bae wrote:
> On 3/10/2022 10:34 AM, Rafael J. Wysocki wrote:
> > On Wed, Mar 9, 2022 at 11:42 PM Chang S. Bae <chang.seok.bae@...el.com>
> > wrote:
> > >
> [...]
> > > @@ -792,7 +805,8 @@ static struct cpuidle_state spr_cstates[] __initdata =
> > > {
> > > {
> > > .name = "C6",
> > > .desc = "MWAIT 0x20",
> > > - .flags = MWAIT2flg(0x20) | CPUIDLE_FLAG_TLB_FLUSHED,
> > > + .flags = MWAIT2flg(0x20) | CPUIDLE_FLAG_TLB_FLUSHED | \
> >
> > Why is the backslash at the end of the line needed?
>
> No, it is not needed.
>
> Sorry, I think I was mindlessly following the style in this new c-state
> table:
> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-
> pm.git/tree/drivers/idle/intel_idle.c?h=linux-next#n787
>
> Thanks,
> Chang
>
Sorry, too much python programming lately, so I automatically added the back-
slash. Let me know if you would remove that backslash at the same time, or I can
submit a patch.
Artem.
Powered by blists - more mailing lists