All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: David Oberhollenzer <goliath@infraroot.at>,
	linux-rt-users@vger.kernel.org, williams@redhat.com,
	richard@nod.at
Subject: Re: [PATCH 0/4] Backport MEMCG changes from v5.17
Date: Fri, 29 Jul 2022 18:14:51 +0200	[thread overview]
Message-ID: <YuQHe3g3Ydmljx7M@linutronix.de> (raw)
In-Reply-To: <60f230fb-de97-ead8-b3a3-12a591804c32@canonical.com>

On 2022-07-27 16:35:44 [-0400], Joseph Salisbury wrote:
> Hi David,
Hi,

> Do you know if these patches will be merged into the 5.15 patchset?

I'm going to look at these next week. Has this been tested?

> Thanks,
> 
> Joe

Sebastian

  reply	other threads:[~2022-07-29 16:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 11:22 [PATCH 0/4] Backport MEMCG changes from v5.17 David Oberhollenzer
2022-07-12 11:22 ` [PATCH 1/4] mm/memcg: Disable threshold event handlers on PREEMPT_RT David Oberhollenzer
2022-07-12 11:22 ` [PATCH 2/4] mm/memcg: Protect per-CPU counter by disabling preemption on PREEMPT_RT where needed David Oberhollenzer
2022-07-12 11:22 ` [PATCH 3/4] mm/memcg: Add a local_lock_t for IRQ and TASK object David Oberhollenzer
2022-07-12 11:22 ` [PATCH 4/4] Allow MEMCG on PREEMPT_RT David Oberhollenzer
2022-07-27 20:35 ` [PATCH 0/4] Backport MEMCG changes from v5.17 Joseph Salisbury
2022-07-29 16:14   ` Sebastian Andrzej Siewior [this message]
2022-07-29 16:37     ` Joseph Salisbury
2022-08-01 18:17     ` Joseph Salisbury
2022-08-01 22:36       ` Joseph Salisbury
2022-08-02 12:28         ` Clark Williams
2022-08-03  6:53 ` Sebastian Andrzej Siewior
2022-08-03  9:17   ` David Oberhollenzer
2022-08-03  9:37     ` Sebastian Andrzej Siewior

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=YuQHe3g3Ydmljx7M@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=goliath@infraroot.at \
    --cc=joseph.salisbury@canonical.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=williams@redhat.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 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.