From: Harry Wentland <harry.wentland@amd.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Leo Li <sunpeng.li@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
stable@vger.kernel.org, Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>
Subject: Re: [Intel-gfx] [PATCH] drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits
Date: Thu, 1 Feb 2018 09:29:43 -0500 [thread overview]
Message-ID: <02ca3511-36c2-d24d-c1d4-9fe30d442d9d@amd.com> (raw)
In-Reply-To: <8d78222f-d598-b2f4-9351-be90b9e9f23f@linux.intel.com>
On 2018-02-01 05:30 AM, Maarten Lankhorst wrote:
> Op 31-01-18 om 20:57 schreef Harry Wentland:
>> On 2018-01-30 05:28 AM, Maarten Lankhorst wrote:
>>> Op 29-01-18 om 16:41 schreef Leo Li:
>>>> Updated IGT results seem sane:
>>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7698/shards.html
>>>>
>>>> Would someone be able to apply this patch?
>>>>
>>> Thanks for the reminder, pushed.
>>>
>> Thanks, Maarten. I see it in drm-misc-next.
>>
>> Would someone be able to pull this into drm-misc-fixes as well, or can I just I apply this myself with the following dim commands?
>>
>> dim checkout drm-misc-fixes
>> dim cherry-pick 1c6ceeee6ebb
>> dim push-branch
> My bad, pushed to the right branch. :)
>
Thanks, Maarten.
Harry
next prev parent reply other threads:[~2018-02-01 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 11:51 [PATCH] drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits Maarten Lankhorst
2018-01-17 12:12 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-17 14:30 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-01-17 16:13 ` ✓ Fi.CI.BAT: success " Patchwork
2018-01-17 18:29 ` [Intel-gfx] [PATCH] " Sean Paul
2018-01-17 18:29 ` Sean Paul
2018-01-17 18:39 ` [Intel-gfx] " Maarten Lankhorst
2018-01-17 20:18 ` Sean Paul
2018-01-29 15:41 ` Leo Li
2018-01-30 10:28 ` Maarten Lankhorst
2018-01-31 19:57 ` Harry Wentland
2018-01-31 19:57 ` Harry Wentland
2018-02-01 10:30 ` [Intel-gfx] " Maarten Lankhorst
2018-02-01 10:30 ` Maarten Lankhorst
2018-02-01 14:29 ` Harry Wentland [this message]
2018-01-25 11:14 ` ✗ Fi.CI.IGT: warning for " Patchwork
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=02ca3511-36c2-d24d-c1d4-9fe30d442d9d@amd.com \
--to=harry.wentland@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=seanpaul@chromium.org \
--cc=stable@vger.kernel.org \
--cc=sunpeng.li@amd.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 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.