From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx-bounces@lists.freedesktop.org,
Zhenyu Wang <zhenyuw@linux.intel.com>,
"Yuan, Hang" <hang.yuan@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915/gvt: declare gvt as i915's soft dependency
Date: Thu, 05 Jul 2018 15:30:52 +0300 [thread overview]
Message-ID: <87zhz5ooeb.fsf@intel.com> (raw)
In-Reply-To: <16919284-3cfe-a9d1-7c29-22f5965ea4bd@linux.intel.com>
On Thu, 05 Jul 2018, intel-gfx-bounces@lists.freedesktop.org wrote:
> On 07/05/2018 03:21 PM, Zhenyu Wang wrote:
>> On 2018.07.04 11:07:45 +0800, intel-gfx-bounces@lists.freedesktop.org wrote:
>>> From: Hang Yuan <hang.yuan@linux.intel.com>
>>>
>>> This helps initramfs builder and other tools to know the full dependencies
>>> of i915 and have gvt module loaded with i915.
>>>
>>> v2: add condition and change to pre-dependency (Chris)
>>> v3: move declaration to gvt.c. (Chris)
>>>
>>> Signed-off-by: Hang Yuan <hang.yuan@linux.intel.com>
>>> ---
>>> drivers/gpu/drm/i915/gvt/gvt.c | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/i915/gvt/gvt.c b/drivers/gpu/drm/i915/gvt/gvt.c
>>> index 4e65266..00f487e9 100644
>>> --- a/drivers/gpu/drm/i915/gvt/gvt.c
>>> +++ b/drivers/gpu/drm/i915/gvt/gvt.c
>>> @@ -468,3 +468,10 @@ int intel_gvt_init_device(struct drm_i915_private *dev_priv)
>>> kfree(gvt);
>>> return ret;
>>> }
>>> +
>>> +#if IS_ENABLED(CONFIG_DRM_I915_GVT_KVMGT)
>>> +MODULE_SOFTDEP("pre: kvmgt");
>>> +#elif IS_ENABLED(CONFIG_DRM_I915_GVT_XENGT)
>>> +MODULE_SOFTDEP("pre: xengt");
>>> +#endif
>>> +
>>
>> Why xengt? it's not in upstream at all, so should be splitted and
>> apply to its topic branch only.
> Henry: I understand xengt_mpt is not in upstream but general part of gvt
> like gvt.c is in upstream.
> The change of the patch is in the general part. Do you think so?
AFAICT upstream IS_ENABLED(CONFIG_DRM_I915_GVT_XENGT) is always false;
there's no such 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
prev parent reply other threads:[~2018-07-05 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 3:07 [PATCH v3] drm/i915/gvt: declare gvt as i915's soft dependency hang.yuan
2018-07-04 3:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-07-04 7:17 ` ✓ Fi.CI.IGT: " Patchwork
2018-07-04 9:21 ` [PATCH v3] " Chris Wilson
2018-07-04 9:30 ` Hang Yuan
2018-07-05 7:21 ` Zhenyu Wang
2018-07-05 7:53 ` Hang Yuan
2018-07-05 12:30 ` 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=87zhz5ooeb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=hang.yuan@intel.com \
--cc=intel-gfx-bounces@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=zhenyuw@linux.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).