Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: netdev@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, chris@chris-wilson.co.uk,
	edumazet@google.com, dri-devel@lists.freedesktop.org,
	rodrigo.vivi@intel.com, kuba@kernel.org, davem@davemloft.net,
	dvyukov@google.com
Subject: Re: [Intel-gfx] [PATCH v9 0/4] drm/i915: use ref_tracker library for tracking wakerefs
Date: Mon, 05 Jun 2023 22:50:22 +0000	[thread overview]
Message-ID: <168600542236.23821.5722558079876009232.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230224-track_gt-v9-0-5b47a33f55d1@intel.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 02 Jun 2023 12:21:32 +0200 you wrote:
> Hi Jakub,
> 
> This is reviewed series of ref_tracker patches, ready to merge
> via network tree, rebased on net-next/main.
> i915 patches will be merged later via intel-gfx tree.
> 
> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
> 
> [...]

Here is the summary with links:
  - [v9,1/4] lib/ref_tracker: add unlocked leak print helper
    https://git.kernel.org/netdev/net-next/c/7a113ff63559
  - [v9,2/4] lib/ref_tracker: improve printing stats
    https://git.kernel.org/netdev/net-next/c/b6d7c0eb2dcb
  - [v9,3/4] lib/ref_tracker: add printing to memory buffer
    https://git.kernel.org/netdev/net-next/c/227c6c832303
  - [v9,4/4] lib/ref_tracker: remove warnings in case of allocation failure
    https://git.kernel.org/netdev/net-next/c/acd8f0e5d727

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-06-20 18:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 10:21 [Intel-gfx] [PATCH v9 0/4] drm/i915: use ref_tracker library for tracking wakerefs Andrzej Hajda
2023-06-02 10:21 ` [Intel-gfx] [PATCH v9 1/4] lib/ref_tracker: add unlocked leak print helper Andrzej Hajda
2023-06-02 10:21 ` [Intel-gfx] [PATCH v9 2/4] lib/ref_tracker: improve printing stats Andrzej Hajda
2023-06-02 18:50   ` Simon Horman
2023-06-02 10:21 ` [Intel-gfx] [PATCH v9 3/4] lib/ref_tracker: add printing to memory buffer Andrzej Hajda
2023-06-02 10:21 ` [Intel-gfx] [PATCH v9 4/4] lib/ref_tracker: remove warnings in case of allocation failure Andrzej Hajda
2023-06-02 11:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: use ref_tracker library for tracking wakerefs (rev10) Patchwork
2023-06-02 11:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-04 10:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-06-05 22:33 ` [Intel-gfx] [PATCH v9 0/4] drm/i915: use ref_tracker library for tracking wakerefs Jakub Kicinski
2023-06-06  6:11   ` Andrzej Hajda
2023-06-05 22:50 ` patchwork-bot+netdevbpf [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=168600542236.23821.5722558079876009232.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrzej.hajda@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rodrigo.vivi@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