From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Yuan, Hang" <hang.yuan@intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PULL] gvt-next-fixes
Date: Thu, 05 Dec 2019 10:14:35 +0200 [thread overview]
Message-ID: <157553367554.5691.10845588295413119546@alackerm-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20191205061141.GF4196@zhen-hp.sh.intel.com>
Quoting Zhenyu Wang (2019-12-05 08:11:41)
>
> ping..
This was pulled, but my dim push was interrupted so I had to re-push and
wait for CI results. Looks all good. Thanks for the PR.
Do you have a plan to start adding Fixes: and Link: tags to the GVT
commits?
Regards, Joonas
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-05 8:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 5:17 [PULL] gvt-next-fixes Zhenyu Wang
2019-12-02 5:17 ` [Intel-gfx] " Zhenyu Wang
2019-12-05 6:11 ` Zhenyu Wang
2019-12-05 8:14 ` Joonas Lahtinen [this message]
2019-12-05 8:49 ` Zhenyu Wang
-- strict thread matches above, loose matches on Subject: below --
2023-04-28 7:47 Zhenyu Wang
2023-02-23 8:50 Zhenyu Wang
2023-02-23 12:11 ` Jani Nikula
2021-04-29 8:51 Zhenyu Wang
2021-04-29 11:12 ` Jani Nikula
2021-04-21 9:45 Zhenyu Wang
2021-04-21 10:51 ` Jani Nikula
2021-02-22 8:34 Zhenyu Wang
2021-02-23 14:42 ` Rodrigo Vivi
2020-12-25 2:20 Zhenyu Wang
2021-01-05 7:54 ` Zhenyu Wang
2021-01-05 8:36 ` Jani Nikula
2021-01-05 20:44 ` Rodrigo Vivi
2020-08-05 8:02 Zhenyu Wang
2020-08-06 15:17 ` Jani Nikula
2020-05-28 3:35 Zhenyu Wang
2020-06-02 14:04 ` Joonas Lahtinen
2020-03-31 7:00 Zhenyu Wang
2020-03-31 16:26 ` Rodrigo Vivi
2020-04-03 3:05 ` Zhenyu Wang
2020-04-03 17:50 ` Rodrigo Vivi
2020-04-07 8:02 ` Zhenyu Wang
2020-04-07 13:35 ` Rodrigo Vivi
2020-04-07 13:53 ` Jani Nikula
2020-04-07 23:36 ` Zhenyu Wang
2019-11-12 6:20 Zhenyu Wang
2019-11-12 6:20 ` [Intel-gfx] " Zhenyu Wang
2019-11-20 11:25 ` Joonas Lahtinen
2019-11-20 11:25 ` [Intel-gfx] " Joonas Lahtinen
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=157553367554.5691.10845588295413119546@alackerm-mobl1.ger.corp.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=hang.yuan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhiyuan.lv@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;
as well as URLs for NNTP newsgroup(s).