public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Maarten Lankhorst <dev@lankhorst.se>
Cc: "Friedrich Vock" <friedrich.vock@gmx.de>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Simona Vetter" <simona.vetter@ffwll.ch>,
	"David Airlie" <airlied@gmail.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	dri-devel@lists.freedesktop.org, cgroups@vger.kernel.org
Subject: Re: [PATCH v2] cgroup/dmem: Don't open-code css_for_each_descendant_pre
Date: Tue, 18 Feb 2025 08:39:58 -1000	[thread overview]
Message-ID: <Z7TT_lFL6hu__NP-@slm.duckdns.org> (raw)
In-Reply-To: <7f799ba1-3776-49bd-8a53-dc409ef2afe3@lankhorst.se>

Hello,

On Tue, Feb 18, 2025 at 03:55:43PM +0100, Maarten Lankhorst wrote:
> Should this fix go through the cgroup tree?

I haven't been routing any dmem patches. Might as well stick to drm tree?

Thanks.

-- 
tejun

  reply	other threads:[~2025-02-18 18:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 15:39 [PATCH] cgroup/dmem: Don't clobber pool in dmem_cgroup_calculate_protection Friedrich Vock
2025-01-14 15:58 ` Michal Koutný
2025-01-16  8:20   ` Friedrich Vock
2025-01-17 17:29     ` Michal Koutný
2025-01-17 19:02       ` Friedrich Vock
2025-01-24  9:56         ` Michal Koutný
2025-01-26 16:38           ` Friedrich Vock
2025-01-27 15:27 ` [PATCH v2] cgroup/dmem: Don't open-code css_for_each_descendant_pre Friedrich Vock
2025-02-12  8:40   ` Maarten Lankhorst
2025-02-18 14:55   ` Maarten Lankhorst
2025-02-18 18:39     ` Tejun Heo [this message]
2025-02-19  8:53       ` Maarten Lankhorst
2025-02-19  9:08       ` Maxime Ripard
2025-02-19 13:26         ` Simona Vetter

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=Z7TT_lFL6hu__NP-@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=airlied@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=dev@lankhorst.se \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=friedrich.vock@gmx.de \
    --cc=hannes@cmpxchg.org \
    --cc=mkoutny@suse.com \
    --cc=mripard@kernel.org \
    --cc=simona.vetter@ffwll.ch \
    /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