From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<linux-pm@vger.kernel.org>
Cc: <tglx@linutronix.de>, <dave.hansen@linux.intel.com>,
<peterz@infradead.org>, <bp@alien8.de>, <rafael@kernel.org>,
<riel@fb.com>, <bigeasy@linutronix.de>, <hch@lst.de>,
<fenghua.yu@intel.com>, <rui.zhang@intel.com>,
<jacob.jun.pan@linux.intel.com>, <lenb@kernel.org>
Subject: Re: [PATCH v5 2/2] intel_idle: Add a new flag to initialize the AMX state
Date: Tue, 14 Jun 2022 10:23:05 -0700 [thread overview]
Message-ID: <b5dea7bb-239d-9054-7130-03a9d1421bf5@intel.com> (raw)
In-Reply-To: <38cd51750ef7b995506d001eae3e4ec872cf5b77.camel@linux.intel.com>
On 6/10/2022 3:02 AM, Artem Bityutskiy wrote:
>
> LGTM,
>
> Reviewed-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Thanks, Artem!
Chang
next prev parent reply other threads:[~2022-06-14 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 16:47 [PATCH v5 0/2] x86/fpu: Make AMX state ready for CPU idle Chang S. Bae
2022-06-08 16:47 ` [PATCH v5 1/2] x86/fpu: Add a helper to prepare AMX state for low-power " Chang S. Bae
2022-06-08 19:32 ` [tip: x86/fpu] " tip-bot2 for Chang S. Bae
2022-06-14 22:46 ` tip-bot2 for Chang S. Bae
2022-06-14 22:53 ` tip-bot2 for Chang S. Bae
2022-07-19 17:31 ` tip-bot2 for Chang S. Bae
2022-06-08 16:47 ` [PATCH v5 2/2] intel_idle: Add a new flag to initialize the AMX state Chang S. Bae
2022-06-08 19:32 ` [tip: x86/fpu] " tip-bot2 for Chang S. Bae
2022-06-09 10:23 ` Peter Zijlstra
2022-06-14 16:41 ` [PATCH][Rebased] " Chang S. Bae
2022-07-19 17:31 ` [tip: x86/fpu] " tip-bot2 for Chang S. Bae
[not found] ` <38cd51750ef7b995506d001eae3e4ec872cf5b77.camel@linux.intel.com>
2022-06-14 17:23 ` Chang S. Bae [this message]
2022-06-15 6:25 ` [PATCH v5 2/2] " Artem Bityutskiy
2022-06-14 22:53 ` [tip: x86/fpu] " tip-bot2 for Chang S. Bae
2022-07-18 9:06 ` Borislav Petkov
2022-07-18 18:56 ` [PATCH][Rebased] " Chang S. Bae
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5dea7bb-239d-9054-7130-03a9d1421bf5@intel.com \
--to=chang.seok.bae@intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hch@lst.de \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=riel@fb.com \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox