From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [GIT PULL] gvt final fixes for 4.13
Date: Wed, 23 Aug 2017 12:29:16 +0300 [thread overview]
Message-ID: <871so24opf.fsf@nikula.org> (raw)
In-Reply-To: <20170823075352.nlo7hp3bplnb5ilx@zhen-hp.sh.intel.com>
On Wed, 23 Aug 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi, here's one final gvt fix for 4.13. One possible null ptr
> reference issue fixed by Fred.
Pulled to drm-intel-fixes, thanks.
BR,
Jani.
>
> Thanks
> --
> The following changes since commit d6086598d34e1cf9091c7be201f5b2041dc6203e:
>
> drm/i915/gvt: Change the max length of mmio_reg_rw from 4 to 8 (2017-08-07 15:50:39 +0800)
>
> are available in the git repository at:
>
> https://github.com/01org/gvt-linux.git tags/gvt-fixes-2017-08-23
>
> for you to fetch changes up to ffeaf9aaf97b4bdaf114d6df52f800d71918768c:
>
> drm/i915/gvt: Fix the kernel null pointer error (2017-08-23 14:08:57 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2017-08-23
>
> - Fix possible null ptr reference in error path (Fred)
>
> ----------------------------------------------------------------
> fred gao (1):
> drm/i915/gvt: Fix the kernel null pointer error
>
> drivers/gpu/drm/i915/gvt/cmd_parser.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-08-23 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 7:53 [GIT PULL] gvt final fixes for 4.13 Zhenyu Wang
2017-08-23 9:29 ` 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=871so24opf.fsf@nikula.org \
--to=jani.nikula@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 \
/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.