From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915/gvt: remove unused to_gvt() and reduce includes
Date: Wed, 11 Oct 2023 14:36:29 +0300 [thread overview]
Message-ID: <87lec94chu.fsf@intel.com> (raw)
In-Reply-To: <ZSZgisH1n0L0jwoq@debian-scheme>
On Wed, 11 Oct 2023, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2023.10.11 10:04:09 +0300, Jani Nikula wrote:
>> On Wed, 11 Oct 2023, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
>> > On 2023.10.04 15:54:11 +0300, Jani Nikula wrote:
>> >> On Tue, 26 Sep 2023, Jani Nikula <jani.nikula@intel.com> wrote:
>> >> > gvt.h has no need to include i915_drv.h once the unused to_gvt() has
>> >> > been removed.
>> >> >
>> >> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> >>
>> >> Zhenyu, Zhi, ping?
>> >>
>> >
>> > Sorry for late reply, as last week was full holiday here.
>> >
>> > Reviewed-by: Zhenyu Wang <zhenyuw@linux.intel.com>
>> >
>> > I don't think I need to do extra pick and pull request for this or
>> > let me know if you has question.
>>
>> Did you pick them up to gvt-next or shall I pick them up to
>> drm-intel-next?
>>
>> If the former, I think I'd actually like a pull request, because
>> otherwise the trees will be out-of-sync for a long time.
>>
>
> Sorry, I mean it's fine for me if you directly pick them for drm-intel-next.
Thanks for the review, pushed to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2023-10-11 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 12:19 [Intel-gfx] [PATCH 1/4] drm/i915/gvt: remove unused to_gvt() and reduce includes Jani Nikula
2023-09-26 12:19 ` [Intel-gfx] [PATCH 2/4] drm/i915/gvt: don't include gvt.h from intel_gvt_mmio_table.h Jani Nikula
2023-09-26 12:19 ` [Intel-gfx] [PATCH 3/4] drm/i915/gvt: move struct engine_mmio to mmio_context.c Jani Nikula
2023-09-26 12:19 ` [Intel-gfx] [PATCH 4/4] drm/i915/gvt: move structs intel_gvt_irq_info and intel_gvt_irq_map to interrupt.c Jani Nikula
2023-09-26 20:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915/gvt: remove unused to_gvt() and reduce includes Patchwork
2023-09-27 8:34 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-04 12:54 ` [Intel-gfx] [PATCH 1/4] " Jani Nikula
2023-10-04 16:03 ` Wang, Zhi A
2023-10-04 16:33 ` Jani Nikula
2023-10-04 17:02 ` Wang, Zhi A
2023-10-11 5:07 ` Zhenyu Wang
2023-10-11 7:04 ` Jani Nikula
2023-10-11 8:44 ` Zhenyu Wang
2023-10-11 11:36 ` 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=87lec94chu.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox