From: Dave Hansen <dave.hansen@intel.com>
To: Yosry Ahmed <yosryahmed@google.com>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH tip:x86/mm v3 1/3] x86/mm: Use IPIs to synchronize LAM enablement
Date: Thu, 9 May 2024 11:22:51 -0700 [thread overview]
Message-ID: <9531f1fc-f91e-40ce-9432-5bcbba2fe2f7@intel.com> (raw)
In-Reply-To: <CAJD7tkZmDQi2HBOxe5u-Lji88NDuZKCQ_=N_O5aE1nq23aUPqw@mail.gmail.com>
On 5/6/24 07:37, Yosry Ahmed wrote:
> The merge window is approaching, is this patchset ready to be picked
> up? Is any further action needed?
Yosry, the merge window is when we send content to Linus. We generally
create that content weeks or months before the merge window.
The best action on your here would be to touch base with Andy and make
sure he's on board with the solution you think he suggested.
next prev parent reply other threads:[~2024-05-09 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 1:28 Yosry Ahmed
2024-04-18 1:28 ` [PATCH tip:x86/mm v3 2/3] x86/mm: Fix LAM inconsistency during context switch Yosry Ahmed
2024-04-18 1:28 ` [PATCH tip:x86/mm v3 3/3] x86/mm: Cleanup prctl_enable_tagged_addr() nr_bits error checking Yosry Ahmed
2024-05-06 14:37 ` [PATCH tip:x86/mm v3 1/3] x86/mm: Use IPIs to synchronize LAM enablement Yosry Ahmed
2024-05-09 18:22 ` Dave Hansen [this message]
2024-05-09 18:28 ` Yosry Ahmed
2024-06-03 22:20 ` Yosry Ahmed
2024-06-24 11:19 ` Yosry Ahmed
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=9531f1fc-f91e-40ce-9432-5bcbba2fe2f7@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yosryahmed@google.com \
/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