From: Jani Nikula <jani.nikula@intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: manasi.d.navare@intel.com, vinod.govindapillai@intel.com,
dri-devel@lists.freedesktop.org, Stanislav.Lisovskiy@intel.com,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
jani.saarinen@intel.com
Subject: Re: [PATCH 0/4] Add DP MST DSC support to i915
Date: Mon, 12 Sep 2022 11:48:44 +0300 [thread overview]
Message-ID: <87wna9566r.fsf@intel.com> (raw)
In-Reply-To: <87v8q08q6w.fsf@intel.com>
On Tue, 06 Sep 2022, Jani Nikula <jani.nikula@intel.com> wrote:
> We'll need to have a clean baseline to apply the patches on, i.e.
> drm-misc-next pull request to drm-next, and drm-next backmerge to
> drm-intel-next.
Stan, this is now done, drm-intel-next has the baseline for your
changes.
Please re-send the series, Cc: dri-devel, and please do get the drm-misc
maintainer ack on the first patch before merging.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-09-12 8:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 8:57 [PATCH 0/4] Add DP MST DSC support to i915 Stanislav Lisovskiy
2022-09-05 8:57 ` [PATCH 1/4] drm: Add missing DP DSC extended capability definitions Stanislav Lisovskiy
2022-09-06 14:35 ` Jani Nikula
2022-09-06 14:37 ` Jani Nikula
2022-09-06 15:43 ` Jani Nikula
2022-09-06 16:50 ` Lisovskiy, Stanislav
2022-09-06 17:34 ` Jani Nikula
2022-09-05 8:57 ` [PATCH 2/4] drm/i915: Fix intel_dp_mst_compute_link_config Stanislav Lisovskiy
2022-09-05 8:57 ` [PATCH 3/4] drm/i915: Extract drm_dp_atomic_find_vcpi_slots cycle to separate function Stanislav Lisovskiy
2022-09-05 8:57 ` [PATCH 4/4] drm/i915: Add DSC support to MST path Stanislav Lisovskiy
2022-09-06 15:42 ` [PATCH 0/4] Add DP MST DSC support to i915 Jani Nikula
2022-09-12 8:48 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-13 14:14 Stanislav Lisovskiy
2022-09-01 10:11 Stanislav Lisovskiy
2022-08-29 9:58 Stanislav Lisovskiy
2022-08-26 9:20 Stanislav Lisovskiy
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=87wna9566r.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=manasi.d.navare@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stanislav.lisovskiy@intel.com \
--cc=vinod.govindapillai@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;
as well as URLs for NNTP newsgroup(s).