From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fixup kerneldoc in struct i915_gem_context
Date: Wed, 6 Apr 2022 08:37:46 +0100 [thread overview]
Message-ID: <18487536-ccb2-ce68-1586-a68870f56214@linux.intel.com> (raw)
In-Reply-To: <YkxowQIS5SZer86X@phenom.ffwll.local>
On 05/04/2022 17:05, Daniel Vetter wrote:
> On Tue, Apr 05, 2022 at 04:53:45PM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Mixup in rebasing and patchwork re-runs made me push the wrong version of
>> the patch. Or I even forgot to send out the fixed version. Fix it up.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Fixes: 748716041dfa ("drm/i915: Track all user contexts per client")
>> Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>
> You picked the wrong sha1. Sure you're on the right tree? :-)
Yeah, my sha1 was of a fixed version of the patch which I never sent out..
> Fixes: 49bd54b390c2 ("drm/i915: Track all user contexts per client")
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Thanks, pushed.
Regards,
Tvrtko
next prev parent reply other threads:[~2022-04-06 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 15:53 [Intel-gfx] [PATCH] drm/i915: Fixup kerneldoc in struct i915_gem_context Tvrtko Ursulin
2022-04-05 16:05 ` Daniel Vetter
2022-04-06 7:37 ` Tvrtko Ursulin [this message]
2022-04-05 18:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-04-05 18:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-05 22:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=18487536-ccb2-ce68-1586-a68870f56214@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
/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