From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jason Ekstrand <jason@jlekstrand.net>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915: Drop I915_CONTEXT_PARAM_RINGSIZE
Date: Mon, 22 Mar 2021 14:01:47 +0200 [thread overview]
Message-ID: <87wntz5rdg.fsf@intel.com> (raw)
In-Reply-To: <CAOFGe94ggJUBH_+bbxAVLUge8NZQYHK55ZzjnQ2erXhh+r8c=A@mail.gmail.com>
On Sat, 20 Mar 2021, Jason Ekstrand <jason@jlekstrand.net> wrote:
> This reverts commit 88be76cdafc7e60e2e4ed883bfe7e8dd7f35fa3a. This API
Small nit, I think it would be useful to reference commits with the
citation style:
88be76cdafc7 ("drm/i915: Allow userspace to specify ringsize on construction")
I use this monster in my .gitconfig:
[alias]
cite = "!f() { git log -1 '--pretty=format:%H (\"%s\")%n' $1 | sed -e 's/\\([0-f]\\{12\\}\\)[0-f]*/\\1/'; }; f"
With that, 'git cite <committish>' will give you the nice reference with
12 chars of sha1 regardless of core.abbrev config.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jason Ekstrand <jason@jlekstrand.net>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915: Drop I915_CONTEXT_PARAM_RINGSIZE
Date: Mon, 22 Mar 2021 14:01:47 +0200 [thread overview]
Message-ID: <87wntz5rdg.fsf@intel.com> (raw)
In-Reply-To: <CAOFGe94ggJUBH_+bbxAVLUge8NZQYHK55ZzjnQ2erXhh+r8c=A@mail.gmail.com>
On Sat, 20 Mar 2021, Jason Ekstrand <jason@jlekstrand.net> wrote:
> This reverts commit 88be76cdafc7e60e2e4ed883bfe7e8dd7f35fa3a. This API
Small nit, I think it would be useful to reference commits with the
citation style:
88be76cdafc7 ("drm/i915: Allow userspace to specify ringsize on construction")
I use this monster in my .gitconfig:
[alias]
cite = "!f() { git log -1 '--pretty=format:%H (\"%s\")%n' $1 | sed -e 's/\\([0-f]\\{12\\}\\)[0-f]*/\\1/'; }; f"
With that, 'git cite <committish>' will give you the nice reference with
12 chars of sha1 regardless of core.abbrev config.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-03-22 12:01 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 22:38 [Intel-gfx] [PATCH 0/4] drm/i915: uAPI clean-ups part 2 Jason Ekstrand
2021-03-19 22:38 ` Jason Ekstrand
2021-03-19 22:38 ` [Intel-gfx] [PATCH 1/4] drm/i915: Drop I915_CONTEXT_PARAM_RINGSIZE Jason Ekstrand
2021-03-19 22:38 ` Jason Ekstrand
2021-03-20 14:48 ` [Intel-gfx] " Jason Ekstrand
2021-03-20 14:48 ` Jason Ekstrand
2021-03-22 10:52 ` [Intel-gfx] " Matthew Auld
2021-03-22 10:52 ` Matthew Auld
2021-03-22 16:00 ` Jason Ekstrand
2021-03-22 16:00 ` Jason Ekstrand
2021-03-22 12:01 ` Jani Nikula [this message]
2021-03-22 12:01 ` Jani Nikula
2021-03-22 16:01 ` Jason Ekstrand
2021-03-22 16:01 ` Jason Ekstrand
2021-03-22 16:26 ` Daniel Vetter
2021-03-22 16:26 ` Daniel Vetter
2021-03-19 22:38 ` [Intel-gfx] [PATCH 2/4] drm/i915: Drop I915_CONTEXT_PARAM_NO_ZEROMAP Jason Ekstrand
2021-03-19 22:38 ` Jason Ekstrand
2021-03-22 13:00 ` [Intel-gfx] [drm/i915] 014c1518e8: assertion_failure kernel test robot
2021-03-22 13:00 ` kernel test robot
2021-03-22 13:00 ` kernel test robot
2021-03-22 13:00 ` kernel test robot
2021-03-19 22:38 ` [Intel-gfx] [PATCH 3/4] drm/i915: Drop the CONTEXT_CLONE API Jason Ekstrand
2021-03-19 22:38 ` Jason Ekstrand
2021-03-22 11:22 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-22 11:22 ` Tvrtko Ursulin
2021-03-22 14:09 ` Daniel Vetter
2021-03-22 14:09 ` Daniel Vetter
2021-03-22 14:32 ` Tvrtko Ursulin
2021-03-22 14:32 ` Tvrtko Ursulin
2021-03-22 14:57 ` Daniel Vetter
2021-03-22 14:57 ` Daniel Vetter
2021-03-22 15:31 ` Tvrtko Ursulin
2021-03-22 15:31 ` Tvrtko Ursulin
2021-03-22 16:24 ` Jason Ekstrand
2021-03-22 16:24 ` Jason Ekstrand
2021-03-23 9:46 ` Tvrtko Ursulin
2021-03-23 9:46 ` Tvrtko Ursulin
2021-03-22 16:43 ` Daniel Vetter
2021-03-22 16:43 ` Daniel Vetter
2021-03-23 9:14 ` Tvrtko Ursulin
2021-03-23 9:14 ` Tvrtko Ursulin
2021-03-23 13:23 ` Daniel Vetter
2021-03-23 13:23 ` Daniel Vetter
2021-03-23 16:23 ` Tvrtko Ursulin
2021-03-23 16:23 ` Tvrtko Ursulin
2021-03-23 17:50 ` Jason Ekstrand
2021-03-23 17:50 ` Jason Ekstrand
2021-03-19 22:38 ` [Intel-gfx] [PATCH 4/4] drm/i915: Implement SINGLE_TIMELINE with a syncobj Jason Ekstrand
2021-03-19 22:38 ` Jason Ekstrand
2021-03-22 12:28 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-22 12:28 ` Tvrtko Ursulin
2021-03-22 16:10 ` Jason Ekstrand
2021-03-22 16:10 ` Jason Ekstrand
2021-03-23 9:35 ` Tvrtko Ursulin
2021-03-23 9:35 ` Tvrtko Ursulin
2021-03-23 17:44 ` Jason Ekstrand
2021-03-23 17:44 ` Jason Ekstrand
2021-03-22 16:59 ` Daniel Vetter
2021-03-22 16:59 ` Daniel Vetter
2021-03-22 19:12 ` Jason Ekstrand
2021-03-22 19:12 ` Jason Ekstrand
2021-03-23 17:51 ` [Intel-gfx] [PATCH] drm/i915: Implement SINGLE_TIMELINE with a syncobj (v2) Jason Ekstrand
2021-03-23 17:51 ` Jason Ekstrand
2021-03-24 9:28 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-24 9:28 ` Tvrtko Ursulin
2021-03-24 9:52 ` Daniel Vetter
2021-03-24 9:52 ` Daniel Vetter
2021-03-24 11:36 ` Tvrtko Ursulin
2021-03-24 11:36 ` Tvrtko Ursulin
2021-03-24 17:18 ` Jason Ekstrand
2021-03-24 17:18 ` Jason Ekstrand
2021-03-25 9:48 ` Tvrtko Ursulin
2021-03-25 9:48 ` Tvrtko Ursulin
2021-03-25 9:54 ` Daniel Vetter
2021-03-25 9:54 ` Daniel Vetter
2021-03-24 9:46 ` Daniel Vetter
2021-03-24 9:46 ` Daniel Vetter
2021-03-25 21:13 ` Matthew Brost
2021-03-25 21:13 ` Matthew Brost
2021-03-25 22:19 ` [Intel-gfx] " Jason Ekstrand
2021-03-25 22:19 ` Jason Ekstrand
2021-03-25 22:21 ` [Intel-gfx] [PATCH 4/4] drm/i915: Implement SINGLE_TIMELINE with a syncobj (v3) Jason Ekstrand
2021-03-25 22:21 ` Jason Ekstrand
2021-03-19 23:14 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: uAPI clean-ups part 2 Patchwork
2021-03-22 11:55 ` Jani Nikula
2021-03-22 16:11 ` Jason Ekstrand
2021-03-23 21:32 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: uAPI clean-ups part 2 (rev2) Patchwork
2021-03-26 3:01 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: uAPI clean-ups part 2 (rev3) 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=87wntz5rdg.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
/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.