From: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <mhocko@suse.com>
Cc: "Nysal Jan K.A." <nysal@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linuxppc-dev@lists.ozlabs.org,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Mark Brown <broonie@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v2] sched/membarrier: Fix redundant load of membarrier_state
Date: Mon, 18 Nov 2024 10:25:17 +0100 [thread overview]
Message-ID: <20241118092517.GE39245@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <ZzsDEvJn-vauz9gE@tiehlicka>
On Mon, Nov 18, 2024 at 10:04:18AM +0100, Michal Hocko wrote:
> I do not see this patch staged in any tree (e.g. linux-next). Is this on
> its way to be merged?
I only now found it -- it doesn't look super urgent. I'll get it into a
git tree after -rc1.
next prev parent reply other threads:[~2024-11-18 9:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 5:39 [PATCH] sched/membarrier: Fix redundant load of membarrier_state Nysal Jan K.A.
2024-10-25 0:29 ` Michael Ellerman
2024-10-25 2:40 ` Stephen Rothwell
2024-10-25 3:22 ` Segher Boessenkool
2024-10-25 12:40 ` Mathieu Desnoyers
2024-10-25 18:30 ` Nysal Jan K.A.
2024-10-29 5:51 ` [PATCH v2] " Nysal Jan K.A.
2024-10-29 17:51 ` Mathieu Desnoyers
2024-10-29 23:29 ` Michael Ellerman
2024-10-30 13:33 ` Segher Boessenkool
2024-11-18 9:04 ` Michal Hocko
2024-11-18 9:25 ` Peter Zijlstra [this message]
2024-11-18 9:51 ` Michal Hocko
2025-01-09 8:46 ` Michal Hocko
2025-03-03 6:04 ` [PATCH v2 RESEND] " Nysal Jan K.A.
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=20241118092517.GE39245@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=justinstitt@google.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhocko@suse.com \
--cc=morbo@google.com \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nysal@linux.ibm.com \
--cc=rick.p.edgecombe@intel.com \
--cc=segher@kernel.crashing.org \
--cc=sfr@canb.auug.org.au \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.