All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>,
	intel-gfx@lists.freedesktop.org, Zhi Wang <zhi.a.wang@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v7 0/8] drm: Introduce struct drm_device based WARN* and use them in i915
Date: Mon, 24 Feb 2020 19:01:53 +0800	[thread overview]
Message-ID: <20200224110153.GB19516@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <87mu98tf3q.fsf@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 902 bytes --]

On 2020.02.24 13:11:05 +0200, Jani Nikula wrote:
> On Mon, 24 Feb 2020, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> > On 2020.02.23 18:09:35 +0200, Jani Nikula wrote:
> >> On Thu, 20 Feb 2020, Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com> wrote:
> >> >   drm/i915/gvt: Make WARN* drm specific where drm_priv ptr is available
> >> >   drm/i915/gvt: Make WARN* drm specific where vgpu ptr is available
> >> 
> >> Thanks for the patches, pushed everything except these, which are for
> >> Zhenyu & Zhi.
> >> 
> >
> > For GVT changes.
> >
> > Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
> 
> I assume you'll pick these up and merge via gvt tree.
> 

yep, I've picked them for -next tree, will send pull very soon
after gvt nightly validation cycle.

thanks

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v7 0/8] drm: Introduce struct drm_device based WARN* and use them in i915
Date: Mon, 24 Feb 2020 19:01:53 +0800	[thread overview]
Message-ID: <20200224110153.GB19516@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <87mu98tf3q.fsf@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 902 bytes --]

On 2020.02.24 13:11:05 +0200, Jani Nikula wrote:
> On Mon, 24 Feb 2020, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> > On 2020.02.23 18:09:35 +0200, Jani Nikula wrote:
> >> On Thu, 20 Feb 2020, Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com> wrote:
> >> >   drm/i915/gvt: Make WARN* drm specific where drm_priv ptr is available
> >> >   drm/i915/gvt: Make WARN* drm specific where vgpu ptr is available
> >> 
> >> Thanks for the patches, pushed everything except these, which are for
> >> Zhenyu & Zhi.
> >> 
> >
> > For GVT changes.
> >
> > Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
> 
> I assume you'll pick these up and merge via gvt tree.
> 

yep, I've picked them for -next tree, will send pull very soon
after gvt nightly validation cycle.

thanks

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-02-24 11:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 16:54 [Intel-gfx] [PATCH v7 0/8] drm: Introduce struct drm_device based WARN* and use them in i915 Pankaj Bharadiya
2020-02-20 16:54 ` Pankaj Bharadiya
2020-02-20 16:55 ` [Intel-gfx] [PATCH v7 1/8] drm/i915/display/cdclk: Make WARN* drm specific where drm_priv ptr is available Pankaj Bharadiya
2020-02-20 16:55   ` Pankaj Bharadiya
2020-02-20 16:55 ` [Intel-gfx] [PATCH v7 2/8] drm/i915/display/ddi: Make WARN* drm specific where drm_device " Pankaj Bharadiya
2020-02-20 16:55   ` Pankaj Bharadiya
2020-02-20 16:55 ` [Intel-gfx] [PATCH v7 3/8] drm/i915/display/display: " Pankaj Bharadiya
2020-02-20 16:55   ` Pankaj Bharadiya
2020-02-20 16:55 ` [Intel-gfx] [PATCH v7 4/8] drm/i915/display/power: Make WARN* drm specific where drm_priv " Pankaj Bharadiya
2020-02-20 16:55   ` Pankaj Bharadiya
2020-02-20 16:55 ` [Intel-gfx] [PATCH v7 5/8] drm/i915/display/dp: Make WARN* drm specific where drm_device " Pankaj Bharadiya
2020-02-20 16:55   ` Pankaj Bharadiya
2020-02-20 16:55 ` [Intel-gfx] [PATCH v7 6/8] drm/i915/display/hdcp: Make WARN* drm specific where drm_priv " Pankaj Bharadiya
2020-02-20 16:55   ` Pankaj Bharadiya
2020-02-20 16:55 ` [Intel-gfx] [PATCH v7 7/8] drm/i915/gvt: " Pankaj Bharadiya
2020-02-20 16:55   ` Pankaj Bharadiya
2020-02-20 16:55 ` [Intel-gfx] [PATCH v7 8/8] drm/i915/gvt: Make WARN* drm specific where vgpu " Pankaj Bharadiya
2020-02-20 16:55   ` Pankaj Bharadiya
2020-02-20 21:26 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: Introduce struct drm_device based WARN* and use them in i915 (rev7) Patchwork
2020-02-20 22:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-23  7:57 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-02-23 16:09 ` [Intel-gfx] [PATCH v7 0/8] drm: Introduce struct drm_device based WARN* and use them in i915 Jani Nikula
2020-02-23 16:09   ` Jani Nikula
2020-02-24  9:57   ` Zhenyu Wang
2020-02-24  9:57     ` Zhenyu Wang
2020-02-24 11:11     ` Jani Nikula
2020-02-24 11:11       ` Jani Nikula
2020-02-24 11:01       ` Zhenyu Wang [this message]
2020-02-24 11:01         ` Zhenyu Wang

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=20200224110153.GB19516@zhen-hp.sh.intel.com \
    --to=zhenyuw@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=pankaj.laxminarayan.bharadiya@intel.com \
    --cc=zhi.a.wang@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.