From: Jason Gunthorpe <jgg@nvidia.com>
To: zhi.wang.linux@gmail.com
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, "'Xu,
Terrence'" <terrence.xu@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
'Christoph Hellwig' <hch@lst.de>
Subject: Re: [Intel-gfx] [PATCH v4 1/2] i915/gvt: Introduce the mmio_info_table.c to support VFIO new mdev API
Date: Mon, 24 Jan 2022 09:18:02 -0400 [thread overview]
Message-ID: <20220124131802.GA966497@nvidia.com> (raw)
In-Reply-To: <004201d8110a$db3ec9e0$91bc5da0$@gmail.com>
On Mon, Jan 24, 2022 at 12:12:12PM +0200, zhi.wang.linux@gmail.com wrote:
> Hi Christoph and Jason:
>
> Have been talking with Raj. I am going to work on this series this week.
Thanks!
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: zhi.wang.linux@gmail.com
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, "'Vivi,
Rodrigo'" <rodrigo.vivi@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
'Christoph Hellwig' <hch@lst.de>,
"'Wang, Zhi A'" <zhi.a.wang@intel.com>
Subject: Re: [PATCH v4 1/2] i915/gvt: Introduce the mmio_info_table.c to support VFIO new mdev API
Date: Mon, 24 Jan 2022 09:18:02 -0400 [thread overview]
Message-ID: <20220124131802.GA966497@nvidia.com> (raw)
In-Reply-To: <004201d8110a$db3ec9e0$91bc5da0$@gmail.com>
On Mon, Jan 24, 2022 at 12:12:12PM +0200, zhi.wang.linux@gmail.com wrote:
> Hi Christoph and Jason:
>
> Have been talking with Raj. I am going to work on this series this week.
Thanks!
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: zhi.wang.linux@gmail.com
Cc: 'Christoph Hellwig' <hch@lst.de>,
"'Wang, Zhi A'" <zhi.a.wang@intel.com>,
intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
'Jani Nikula' <jani.nikula@linux.intel.com>,
'Joonas Lahtinen' <joonas.lahtinen@linux.intel.com>,
"'Vivi, Rodrigo'" <rodrigo.vivi@intel.com>,
'Zhenyu Wang' <zhenyuw@linux.intel.com>,
"'Xu, Terrence'" <terrence.xu@intel.com>
Subject: Re: [PATCH v4 1/2] i915/gvt: Introduce the mmio_info_table.c to support VFIO new mdev API
Date: Mon, 24 Jan 2022 09:18:02 -0400 [thread overview]
Message-ID: <20220124131802.GA966497@nvidia.com> (raw)
In-Reply-To: <004201d8110a$db3ec9e0$91bc5da0$@gmail.com>
On Mon, Jan 24, 2022 at 12:12:12PM +0200, zhi.wang.linux@gmail.com wrote:
> Hi Christoph and Jason:
>
> Have been talking with Raj. I am going to work on this series this week.
Thanks!
Jason
next prev parent reply other threads:[~2022-01-24 13:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 12:38 [Intel-gfx] [PATCH v4 1/2] i915/gvt: Introduce the mmio_info_table.c to support VFIO new mdev API Zhi Wang
2021-11-29 12:38 ` Zhi Wang
2021-11-29 12:38 ` Zhi Wang
2021-11-29 12:38 ` [Intel-gfx] [PATCH v4 2/2] i915/gvt: save the MMIO snapshot in the early init of GVT-g Zhi Wang
2021-11-29 12:38 ` Zhi Wang
2021-11-29 12:38 ` Zhi Wang
2021-11-29 12:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v4,1/2] i915/gvt: Introduce the mmio_info_table.c to support VFIO new mdev API Patchwork
2021-11-29 13:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-29 14:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-11-30 16:46 ` [Intel-gfx] [PATCH v4 1/2] " Christoph Hellwig
2021-11-30 16:46 ` Christoph Hellwig
2021-12-17 8:52 ` [Intel-gfx] " Wang, Zhi A
2021-12-17 8:52 ` Wang, Zhi A
2021-12-17 8:52 ` Wang, Zhi A
2022-01-24 9:40 ` [Intel-gfx] " Christoph Hellwig
2022-01-24 9:40 ` Christoph Hellwig
2022-01-24 10:12 ` [Intel-gfx] " zhi.wang.linux
2022-01-24 10:12 ` zhi.wang.linux
2022-01-24 10:12 ` zhi.wang.linux
2022-01-24 13:18 ` Jason Gunthorpe [this message]
2022-01-24 13:18 ` Jason Gunthorpe
2022-01-24 13:18 ` Jason Gunthorpe
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=20220124131802.GA966497@nvidia.com \
--to=jgg@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrence.xu@intel.com \
--cc=zhi.wang.linux@gmail.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.