From: Tejun Heo <tj@kernel.org>
To: Natalie Vock <natalie.vock@gmx.de>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maarten Lankhorst" <dev@lankhorst.se>,
"Maxime Ripard" <mripard@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Christian Koenig" <christian.koenig@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
"Matthew Auld" <matthew.auld@intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
cgroups@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 2/6] cgroup,cgroup/dmem: Add (dmem_)cgroup_common_ancestor helper
Date: Tue, 10 Mar 2026 06:42:02 -1000 [thread overview]
Message-ID: <abBJ2ozm3QS2ozki@slm.duckdns.org> (raw)
In-Reply-To: <5b8f3944-edb3-4b14-85a6-060295e0237a@gmx.de>
On Tue, Mar 10, 2026 at 01:48:47PM +0100, Natalie Vock wrote:
> Hi,
>
> On 3/5/26 21:02, Natalie Vock wrote:
> > On 3/2/26 15:38, Maarten Lankhorst wrote:
> > > Hey,
> > >
> > > This should probably have a Co-developed-by: Tejun Heo <tj@kernel.org>
> >
> > Oh, that's a good point, sorry!
> >
> > Although, I think I also need to add a S-o-b tag, then, don't I?
> >
> > Tejun, just to confirm, would you be fine with that? Wouldn't want to
> > claim people certify something without talking to them first :P
>
> Friendly ping on this :)
>
> I intend to send out a new version with the outstanding feedback addressed,
> although I'd like to resolve this before I do that.
Sorry about the delay. It doesn't really matter. No need to attribute
anything.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-03-10 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 12:37 [PATCH v5 0/6] cgroup/dmem,drm/ttm: Improve protection in contended cases Natalie Vock
2026-03-02 12:37 ` [PATCH v5 1/6] cgroup/dmem: Add queries for protection values Natalie Vock
2026-03-11 1:12 ` Chen Ridong
2026-03-11 8:33 ` Natalie Vock
2026-03-12 0:36 ` Chen Ridong
2026-03-02 12:37 ` [PATCH v5 2/6] cgroup,cgroup/dmem: Add (dmem_)cgroup_common_ancestor helper Natalie Vock
2026-03-02 14:38 ` Maarten Lankhorst
2026-03-05 20:02 ` Natalie Vock
2026-03-10 12:48 ` Natalie Vock
2026-03-10 16:42 ` Tejun Heo [this message]
2026-03-02 12:37 ` [PATCH v5 3/6] drm/ttm: Extract code for attempting allocation in a place Natalie Vock
2026-03-02 15:08 ` Tvrtko Ursulin
2026-03-02 12:37 ` [PATCH v5 4/6] drm/ttm: Split cgroup charge and resource allocation Natalie Vock
2026-03-02 15:25 ` Tvrtko Ursulin
2026-03-02 12:37 ` [PATCH v5 5/6] drm/ttm: Be more aggressive when allocating below protection limit Natalie Vock
2026-03-02 17:02 ` Tvrtko Ursulin
2026-03-13 11:39 ` Natalie Vock
2026-03-02 12:37 ` [PATCH v5 6/6] drm/ttm: Use common ancestor of evictor and evictee as limit pool Natalie Vock
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=abBJ2ozm3QS2ozki@slm.duckdns.org \
--to=tj@kernel.org \
--cc=airlied@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=christian.koenig@amd.com \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=hannes@cmpxchg.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=mkoutny@suse.com \
--cc=mripard@kernel.org \
--cc=natalie.vock@gmx.de \
--cc=ray.huang@amd.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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