From: Jani Nikula <jani.nikula@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
"Yuan, Hang" <hang.yuan@intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [PULL] gvt-fixes for 4.17
Date: Fri, 08 Jun 2018 15:04:08 +0300 [thread overview]
Message-ID: <871sdh5vt3.fsf@intel.com> (raw)
In-Reply-To: <152829069854.9487.6563421636194468462@jlahtine-desk.ger.corp.intel.com>
On Wed, 06 Jun 2018, Joonas Lahtinen <joonas.lahtinen@linux.intel.com> wrote:
> Quoting Zhenyu Wang (2018-06-06 10:49:54)
>> On 2018.04.19 15:39:48 +0800, Zhenyu Wang wrote:
>> >
>> > Hi,
>> >
>> > Here's current gvt fixes for 4.17 with several kernel warning
>> > and other misc fixes as detailed below.
>> >
>> > p.s: I'll be on vacation from next week till May 2, Zhi will cover for me.
>> >
>> > Thanks
>> > --
>>
>> Looks this one got missed for merge...just found when trying to apply new
>> change that caused conflict..Pls help to merge and will request a backmerge
>> to apply -next change against those.
>
> As discussed in IRC, the gvt-next PR was as --in-reply-to for this
> message, so I indeed confused it for being discussion about the gvt-next
> between Jani and Zhi, and missed it :(
So this missed v4.17. I've now pulled this into drm-intel-next-fixes,
and it'll get merged upstream for v4.18. If you need the commits
backported, you'll need to make stable backport requests to the stable
team after the commits have been merged to Linus' master.
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
prev parent reply other threads:[~2018-06-08 12:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 7:39 [PULL] gvt-fixes for 4.17 Zhenyu Wang
2018-04-19 9:17 ` [PULL] gvt-next " Zhi Wang
2018-04-19 9:21 ` Zhi Wang
2018-04-19 9:34 ` Jani Nikula
2018-04-19 9:41 ` Zhenyu Wang
2018-04-19 9:50 ` Zhi Wang
2018-04-19 10:16 ` Zhi Wang
2018-04-23 8:11 ` [PULL] gvt-next for 4.18 Zhi Wang
2018-04-23 8:13 ` Zhi Wang
2018-04-23 10:25 ` Jani Nikula
2018-04-23 16:01 ` Zhi Wang
2018-04-24 10:17 ` Zhi Wang
2018-05-13 22:17 ` Zhi Wang
2018-05-14 8:35 ` Jani Nikula
2018-05-14 12:13 ` Wang, Zhi A
2018-06-06 7:49 ` [PULL] gvt-fixes for 4.17 Zhenyu Wang
2018-06-06 13:11 ` Joonas Lahtinen
2018-06-08 12:04 ` Jani Nikula [this message]
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=871sdh5vt3.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=hang.yuan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@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 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.