From: Yu Kuai <yukuai3@huawei.com> To: <emma@anholt.net>, <airlied@linux.ie>, <daniel@ffwll.ch> Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>, <yukuai3@huawei.com>, <yi.zhang@huawei.com> Subject: [PATCH 0/2] cleanup patches for PM reference leak Date: Mon, 17 May 2021 16:14:36 +0800 [thread overview] Message-ID: <20210517081438.1562410-1-yukuai3@huawei.com> (raw) Yu Kuai (2): drm/v3d: Fix PM reference leak in v3d_get_param_ioctl() drm/v3d: Fix PM reference leak in v3d_v3d_debugfs_ident() drivers/gpu/drm/v3d/v3d_debugfs.c | 4 ++-- drivers/gpu/drm/v3d/v3d_drv.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) -- 2.25.4
WARNING: multiple messages have this Message-ID (diff)
From: Yu Kuai <yukuai3@huawei.com> To: <emma@anholt.net>, <airlied@linux.ie>, <daniel@ffwll.ch> Cc: yukuai3@huawei.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, yi.zhang@huawei.com Subject: [PATCH 0/2] cleanup patches for PM reference leak Date: Mon, 17 May 2021 16:14:36 +0800 [thread overview] Message-ID: <20210517081438.1562410-1-yukuai3@huawei.com> (raw) Yu Kuai (2): drm/v3d: Fix PM reference leak in v3d_get_param_ioctl() drm/v3d: Fix PM reference leak in v3d_v3d_debugfs_ident() drivers/gpu/drm/v3d/v3d_debugfs.c | 4 ++-- drivers/gpu/drm/v3d/v3d_drv.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) -- 2.25.4
next reply other threads:[~2021-05-17 8:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-17 8:14 Yu Kuai [this message] 2021-05-17 8:14 ` [PATCH 0/2] cleanup patches for PM reference leak Yu Kuai 2021-05-17 8:14 ` [PATCH 1/2] drm/v3d: Fix PM reference leak in v3d_get_param_ioctl() Yu Kuai 2021-05-17 8:14 ` Yu Kuai 2021-05-17 8:14 ` [PATCH 2/2] drm/v3d: Fix PM reference leak in v3d_v3d_debugfs_ident() Yu Kuai 2021-05-17 8:14 ` Yu Kuai 2021-05-29 9:11 ` [PATCH 0/2] cleanup patches for PM reference leak yukuai (C) 2021-05-29 9:11 ` yukuai (C) 2021-06-07 9:10 ` yukuai (C) 2021-06-07 9:10 ` yukuai (C)
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=20210517081438.1562410-1-yukuai3@huawei.com \ --to=yukuai3@huawei.com \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=emma@anholt.net \ --cc=linux-kernel@vger.kernel.org \ --cc=yi.zhang@huawei.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.