From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: chris.p.wilson@linux.intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/selftests: Unwind hugepages to drop wakeref on error
Date: Fri, 13 Jan 2023 13:07:53 +0100 [thread overview]
Message-ID: <7a8ad9f3-326d-3f84-0671-ce0ee1a732ea@linux.intel.com> (raw)
In-Reply-To: <e2c3f194-8122-5fe1-c6e4-25d8af867f64@intel.com>
On 1/13/2023 1:05 PM, Matthew Auld wrote:
> On 13/01/2023 12:02, Das, Nirmoy wrote:
>> Thanks Matt, I missed the Fixes tag so resent it with fixes and Cc to
>> stable.
>
> I don't think kernel selftests are really stable material. AFAIK it's
> not something normal users care about.
True, in that case please ignore the latest copy of this patch!.
Thanks,
Nirmoy
>
>>
>> On 1/13/2023 12:51 PM, Matthew Auld wrote:
>>> On 13/01/2023 11:49, Nirmoy Das wrote:
>>>> From: Chris Wilson <chris.p.wilson@linux.intel.com>
>>>>
>>>> Make sure that upon error after we have acquired the wakeref we do
>>>> release it again.
>>>>
>>>> Signed-off-by: Chris Wilson <chris.p.wilson@linux.intel.com>
>>>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2023-01-13 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 11:49 [Intel-gfx] [PATCH] drm/i915/selftests: Unwind hugepages to drop wakeref on error Nirmoy Das
2023-01-13 11:51 ` Matthew Auld
2023-01-13 12:02 ` Das, Nirmoy
2023-01-13 12:05 ` Matthew Auld
2023-01-13 12:07 ` Das, Nirmoy [this message]
2023-01-16 11:21 ` Andrzej Hajda
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 12:00 Nirmoy Das
2023-01-16 18:49 ` Andi Shyti
2023-01-17 8:57 ` Das, Nirmoy
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=7a8ad9f3-326d-3f84-0671-ce0ee1a732ea@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=nirmoy.das@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