From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Wang, Zhi A" <zhi.a.wang@intel.com>,
Christoph Hellwig <hch@lst.de>,
Zhi Wang <zhi.wang.linux@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
Zhi Wang <zhi.a.wang@gmail.com>, Jason Gunthorpe <jgg@nvidia.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>
Subject: Re: [PATCH v7 1/3] i915/gvt: Separate the MMIO tracking table from GVT-g
Date: Thu, 31 Mar 2022 11:25:25 +0300 [thread overview]
Message-ID: <871qyibkay.fsf@intel.com> (raw)
In-Reply-To: <4af59d97-b583-4022-3ec3-360e7df43689@intel.com>
On Thu, 31 Mar 2022, "Wang, Zhi A" <zhi.a.wang@intel.com> wrote:
> Hi Jani and Joonas:
>
> Are you OK with these patches? I noticed I need to change the license
> of the new file. Will do that when check-in if you are OK with these.
Use SPDX license header instead of the full text?
I don't know much about the actual contents, I'll leave that part to
others.
Seems that you are dropping const in a number of places where I thought
you could perhaps retain it.
Also in drivers/gpu/drm/i915/intel_gvt_mmio_table.c:
#include "gvt.h"
looks bad. It should be "gvt/gvt.h". I realize you can do that because
gvt/Makefile has:
ccflags-y += -I $(srctree)/$(src) -I $(srctree)/$(src)/$(GVT_DIR)/
which I think should be removed.
I sent patches fixing this to give you an idea. No need to queue them
first, I can rebase them later. But please make sure this builds without
the ccflags.
BR,
Jani.
>
> Thanks,
> Zhi.
>
> On 3/28/22 6:50 AM, Christoph Hellwig wrote:
>> On Fri, Mar 25, 2022 at 01:52:49PM -0400, Zhi Wang wrote:
>>>
>>> v7:
>>>
>>> - Keep the marcos of device generation in GVT-g. (Christoph, Jani)
>>
>> The changelog go under the "---" line (also for the other patches).
>>
>> Otherwise looks good:
>>
>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>>
>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-03-31 8:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 17:52 [PATCH v7 1/3] i915/gvt: Separate the MMIO tracking table from GVT-g Zhi Wang
2022-03-25 17:52 ` [PATCH v7 2/3] i915/gvt: Save the initial HW state snapshot in i915 Zhi Wang
2022-03-28 6:50 ` Christoph Hellwig
2022-03-25 17:52 ` [PATCH v7 3/3] i915/gvt: Use the initial HW state snapshot saved " Zhi Wang
2022-03-28 6:50 ` Christoph Hellwig
2022-03-26 0:27 ` [PATCH v7 1/3] i915/gvt: Separate the MMIO tracking table from GVT-g kernel test robot
2022-03-26 0:58 ` kernel test robot
2022-03-28 6:50 ` Christoph Hellwig
2022-03-31 7:11 ` Wang, Zhi A
2022-03-31 7:42 ` Christoph Hellwig
2022-03-31 8:04 ` Wang, Zhi A
2022-03-31 8:33 ` Christoph Hellwig
2022-03-31 8:35 ` Zhi Wang
2022-03-31 8:25 ` Jani Nikula [this message]
2022-04-01 13:12 ` Wang, Zhi A
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=871qyibkay.fsf@intel.com \
--to=jani.nikula@linux.intel.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=jgg@nvidia.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@gmail.com \
--cc=zhi.a.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox