From: Christoph Hellwig <hch@lst.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Zhi Wang <zhi.wang.linux@gmail.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Xu, Terrence" <terrence.xu@intel.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Intel-gfx] [PATCH v6 1/3] i915/gvt: Introduce the mmio table to support VFIO new mdev API
Date: Tue, 15 Mar 2022 09:48:17 +0100 [thread overview]
Message-ID: <20220315084817.GA4105@lst.de> (raw)
In-Reply-To: <87a6drvc02.fsf@intel.com>
On Tue, Mar 15, 2022 at 10:46:53AM +0200, Jani Nikula wrote:
> On Tue, 15 Mar 2022, Christoph Hellwig <hch@lst.de> wrote:
> > Just curious, what is the state of this seris? It would be good to
> > have it ready early on for the next merge window as there is quite
> > a backlog that depends on it.
>
> Can't speak for the status of the series, but for drm the deadline for
> changes headed for the merge window is around -rc5/-rc6 timeframe
> i.e. this has already missed the upcoming merge window.
I know. I meant the next one, not the one ending now. And I don't
want to miss another one.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
"Wang, Zhi A" <zhi.a.wang@intel.com>,
Zhi Wang <zhi.wang.linux@gmail.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
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 v6 1/3] i915/gvt: Introduce the mmio table to support VFIO new mdev API
Date: Tue, 15 Mar 2022 09:48:17 +0100 [thread overview]
Message-ID: <20220315084817.GA4105@lst.de> (raw)
In-Reply-To: <87a6drvc02.fsf@intel.com>
On Tue, Mar 15, 2022 at 10:46:53AM +0200, Jani Nikula wrote:
> On Tue, 15 Mar 2022, Christoph Hellwig <hch@lst.de> wrote:
> > Just curious, what is the state of this seris? It would be good to
> > have it ready early on for the next merge window as there is quite
> > a backlog that depends on it.
>
> Can't speak for the status of the series, but for drm the deadline for
> changes headed for the merge window is around -rc5/-rc6 timeframe
> i.e. this has already missed the upcoming merge window.
I know. I meant the next one, not the one ending now. And I don't
want to miss another one.
next prev parent reply other threads:[~2022-03-15 8:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 11:11 [Intel-gfx] [PATCH v6 1/3] i915/gvt: Introduce the mmio table to support VFIO new mdev API Zhi Wang
2022-02-08 11:11 ` Zhi Wang
2022-02-08 11:11 ` Zhi Wang
2022-02-08 11:11 ` [Intel-gfx] [PATCH v6 2/3] i915/gvt: Save the initial HW state snapshot in i915 Zhi Wang
2022-02-08 11:11 ` Zhi Wang
2022-02-08 11:11 ` Zhi Wang
2022-02-09 7:32 ` [Intel-gfx] " Christoph Hellwig
2022-02-09 7:32 ` Christoph Hellwig
2022-02-09 19:50 ` [Intel-gfx] " Wang, Zhi A
2022-02-09 19:50 ` Wang, Zhi A
2022-02-09 19:50 ` Wang, Zhi A
2022-02-08 11:11 ` [Intel-gfx] [PATCH v6 3/3] i915/gvt: Use the initial HW state snapshot saved " Zhi Wang
2022-02-08 11:11 ` Zhi Wang
2022-02-08 11:11 ` Zhi Wang
2022-02-09 7:32 ` [Intel-gfx] " Christoph Hellwig
2022-02-09 7:32 ` Christoph Hellwig
2022-02-08 12:24 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [v6,1/3] i915/gvt: Introduce the mmio table to support VFIO new mdev API Patchwork
2022-02-08 15:15 ` [Intel-gfx] [PATCH v6 1/3] " Jani Nikula
2022-02-08 15:15 ` Jani Nikula
2022-02-08 15:15 ` Jani Nikula
2022-02-09 7:28 ` [Intel-gfx] " Christoph Hellwig
2022-02-09 7:28 ` Christoph Hellwig
2022-02-09 9:04 ` [Intel-gfx] " Jani Nikula
2022-02-09 9:04 ` Jani Nikula
2022-02-09 9:04 ` Jani Nikula
2022-02-09 19:57 ` [Intel-gfx] " Wang, Zhi A
2022-02-09 19:57 ` Wang, Zhi A
2022-02-09 19:57 ` Wang, Zhi A
2022-02-09 19:57 ` [Intel-gfx] " Wang, Zhi A
2022-02-09 19:57 ` Wang, Zhi A
2022-02-09 19:57 ` Wang, Zhi A
2022-03-15 7:52 ` [Intel-gfx] " Christoph Hellwig
2022-03-15 7:52 ` Christoph Hellwig
2022-03-15 8:46 ` [Intel-gfx] " Jani Nikula
2022-03-15 8:46 ` Jani Nikula
2022-03-15 8:46 ` Jani Nikula
2022-03-15 8:48 ` Christoph Hellwig [this message]
2022-03-15 8:48 ` Christoph Hellwig
2022-03-15 8:59 ` [Intel-gfx] " Wang, Zhi A
2022-03-15 8:59 ` Wang, Zhi A
2022-03-15 8:59 ` Wang, Zhi A
2022-03-15 9:16 ` [Intel-gfx] " Jani Nikula
2022-03-15 9:16 ` Jani Nikula
2022-03-15 9:16 ` Jani Nikula
2022-02-09 7:36 ` [Intel-gfx] " Christoph Hellwig
2022-02-09 7:36 ` Christoph Hellwig
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=20220315084817.GA4105@lst.de \
--to=hch@lst.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--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.