Re: [PULL] gvt-next-2022-04-29

[Jani Nikula <jani.nikula@linux.intel.com>]

On Thu, 28 Apr 2022, "Wang, Zhi A" <zhi.a.wang@intel.com> wrote:
> Hi folks:
>
> Here is the pull of gvt-next which fixes the compilation error and warnings
> for the the GVT-g refactor patches: 
>
> - Fix a compiling warning of non-static function only having one caller.
> - Fix a potential NULL pointer reference in the code re-factor.
> - Fix a compiling error when CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
>
> I also tried to apply this pull on the latest drm-inte-next and it succeeded
> without error and warnings.

Thanks again, pulled to drm-intel-next.

BR,
Jani.

>
> The following changes since commit 5e9ae5c47052e28a31fb4f55a6e735c28d4c3948:
>
>   drm/i915/gvt: Add missing symbol export. (2022-04-26 04:18:43 -0400)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux tags/gvt-next-2022-04-29
>
> for you to fetch changes up to 419f8299ddad6070a6c95aaedf78e50265871f36:
>
>   i915/gvt: Fix NULL pointer dereference in init_mmio_block_handlers (2022-04-28 17:06:02 -0400)
>
> ----------------------------------------------------------------
> gvt-next-2022-04-29
>
> Introduce fixes from previous pull.
> - Fix a compiling warning of non-static funtion only having one caller.
> - Fix a potential NULL pointer reference in the code re-factor.
> - Fix a compiling error when CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
>
> ----------------------------------------------------------------
> Wan Jiabing (1):
>       i915/gvt: Fix NULL pointer dereference in init_mmio_block_handlers
>
> Zhi Wang (2):
>       drm/i915/gvt: Make intel_gvt_match_device() static
>       drm/i915/gvt: Fix the compiling error when CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
>
>  drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
>  drivers/gpu/drm/i915/intel_gvt.c    | 2 ++
>  2 files changed, 4 insertions(+), 2 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center