From: Yosry Ahmed <yosryahmed@google.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, 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: Mon, 24 Jun 2024 04:19:11 -0700 [thread overview]
Message-ID: <CAJD7tkbve6kKheCO5ZnqOgU_m6m-DaJH1nG=87EnF+L5HYX2kQ@mail.gmail.com> (raw)
In-Reply-To: <CAJD7tkaVDrc=vioidZHM6KfdCqrCDt-HXn-RussNS145M1fNgg@mail.gmail.com>
On Mon, Jun 3, 2024 at 3:20 PM Yosry Ahmed <yosryahmed@google.com> wrote:
>
> On Thu, May 9, 2024 at 11:28 AM Yosry Ahmed <yosryahmed@google.com> wrote:
> >
> > On Thu, May 9, 2024 at 11:22 AM Dave Hansen <dave.hansen@intel.com> wrote:
> > >
> > > 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.
> >
> > Right. The patch series has been idle for a long time so I assumed it
> > was going to be picked up for this merge window, but given how close
> > we have gotten I think we're past this now.
> >
> > That's fine, I am just trying to get some clarity on whether anything
> > else needs to be done for this to be in a mergeable state.
> >
> > >
> > > 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.
> >
> > I have been slightly pinging the series and/or resending every once in
> > a while, trying not to be too annoying :) Hopefully Andy will voice
> > his opinion.
>
> Hey Dave,
>
> I have tried reaching out to Andy on and off list, and didn't have any
> luck unfortunately :/
>
> Is there any way we can still make progress on getting the fixes in
> this series merged?
Friendly ping on this :)
prev parent reply other threads:[~2024-06-24 11:19 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
2024-05-09 18:28 ` Yosry Ahmed
2024-06-03 22:20 ` Yosry Ahmed
2024-06-24 11:19 ` Yosry Ahmed [this message]
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='CAJD7tkbve6kKheCO5ZnqOgU_m6m-DaJH1nG=87EnF+L5HYX2kQ@mail.gmail.com' \
--to=yosryahmed@google.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--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 \
/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