From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Eric Dumazet <edumazet@google.com>,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
"David S. Miller" <davem@davemloft.net>,
Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [PATCH v8 0/7] drm/i915: use ref_tracker library for tracking wakerefs
Date: Tue, 25 Apr 2023 22:01:15 +0200 [thread overview]
Message-ID: <ZEgxi3+eaG5Xf6bl@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230224-track_gt-v8-0-4b6517e61be6@intel.com>
Hi,
> Andrzej Hajda (7):
> lib/ref_tracker: add unlocked leak print helper
> lib/ref_tracker: improve printing stats
> lib/ref_tracker: add printing to memory buffer
> lib/ref_tracker: remove warnings in case of allocation failure
> drm/i915: Correct type of wakeref variable
> drm/i915: Replace custom intel runtime_pm tracker with ref_tracker library
> drm/i915: Track gt pm wakerefs
where are we going to get this series merged? Should we merge it
in our intel repository? In the netdev repository? or do we split
it (which will cause some dependency delay)?
Andi
next prev parent reply other threads:[~2023-04-25 20:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 22:05 [PATCH v8 0/7] drm/i915: use ref_tracker library for tracking wakerefs Andrzej Hajda
2023-04-24 22:05 ` [PATCH v8 1/7] lib/ref_tracker: add unlocked leak print helper Andrzej Hajda
2023-04-24 22:05 ` [PATCH v8 2/7] lib/ref_tracker: improve printing stats Andrzej Hajda
2023-04-25 12:42 ` Eric Dumazet
2023-04-24 22:05 ` [PATCH v8 3/7] lib/ref_tracker: add printing to memory buffer Andrzej Hajda
2023-04-25 12:44 ` Eric Dumazet
2023-04-24 22:05 ` [PATCH v8 4/7] lib/ref_tracker: remove warnings in case of allocation failure Andrzej Hajda
2023-04-24 22:05 ` [PATCH v8 5/7] drm/i915: Correct type of wakeref variable Andrzej Hajda
2023-04-24 22:05 ` [PATCH v8 6/7] drm/i915: Replace custom intel runtime_pm tracker with ref_tracker library Andrzej Hajda
2023-04-25 19:25 ` Andi Shyti
2023-04-24 22:05 ` [PATCH v8 7/7] drm/i915: Track gt pm wakerefs Andrzej Hajda
2023-04-28 8:55 ` Andi Shyti
2023-04-25 20:01 ` Andi Shyti [this message]
2023-05-04 16:27 ` [Intel-gfx] [PATCH v8 0/7] drm/i915: use ref_tracker library for tracking wakerefs Andrzej Hajda
2023-05-05 20:06 ` Rodrigo Vivi
2023-05-08 17:16 ` Andrzej Hajda
2023-06-01 17:14 ` Andrzej Hajda
2023-06-01 17:18 ` Jakub Kicinski
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=ZEgxi3+eaG5Xf6bl@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).