From: Simona Vetter <simona.vetter@ffwll.ch>
To: Maxime Ripard <mripard@kernel.org>
Cc: "Tejun Heo" <tj@kernel.org>,
"Maarten Lankhorst" <dev@lankhorst.se>,
"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>,
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: Wed, 19 Feb 2025 14:26:59 +0100 [thread overview]
Message-ID: <Z7XcIxX_LDxODXZ9@phenom.ffwll.local> (raw)
In-Reply-To: <20250219-tactful-attractive-goldfish-51f8fc@houat>
On Wed, Feb 19, 2025 at 10:08:57AM +0100, Maxime Ripard wrote:
> On Tue, Feb 18, 2025 at 08:39:58AM -1000, Tejun Heo wrote:
> > 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?
>
> We merged the dmem cgroup through drm because we also had driver
> changes, but going forward, as far as I'm concerned, it's "your" thing,
> and it really shouldn't go through drm
I guess we could also route it through drm-misc. Either way I think we
need a MAINTAINERS entry for dmem so that dri-devel gets cc'ed. And then
make a decision on which git repo should be the standard path. I think
either is fine, but at least for now it looks like most interactions are
between dmem and drm, and not between dmem and cgroups at large. And in
any case we can just ack patches for going the other path on a
case-by-case basis.
Cheers, Sima
--
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2025-02-19 13:27 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
2025-02-19 8:53 ` Maarten Lankhorst
2025-02-19 9:08 ` Maxime Ripard
2025-02-19 13:26 ` Simona Vetter [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=Z7XcIxX_LDxODXZ9@phenom.ffwll.local \
--to=simona.vetter@ffwll.ch \
--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=tj@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