Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Mark Yacoub <markyacoub@chromium.org>,
	intel-gfx@lists.freedesktop.org,
	Douglas Anderson <dianders@chromium.org>,
	seanpaul@chromium.org, dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	freedreno@lists.freedesktop.org,
	Mark Yacoub <markyacoub@google.com>
Subject: Re: [Intel-gfx] [PATCH v10 00/10] drm/hdcp: Pull HDCP auth/exchange/check into helpers
Date: Mon, 22 May 2023 08:59:11 -0400	[thread overview]
Message-ID: <ZGtnH5YJ8u6bMo4j@rdvivi-mobl4> (raw)
In-Reply-To: <27b4bce7-2f63-9199-71e6-4ed52a96d0c1@linaro.org>

On Sat, May 20, 2023 at 02:07:51AM +0300, Dmitry Baryshkov wrote:
> On 20/05/2023 00:16, Rodrigo Vivi wrote:
> > On Fri, May 19, 2023 at 07:55:47PM +0300, Dmitry Baryshkov wrote:
> > > On 19/04/2023 18:43, Mark Yacoub wrote:
> > > > Hi all,
> > > > This is v10 of the HDCP patches. The patches are authored by Sean Paul.
> > > > I rebased and addressed the review comments in v6-v10.
> > > > 
> > > > Main change in v10 is handling the kernel test bot warnings.
> > > > 
> > > > Patches 1-4 focus on moving the common HDCP helpers to common DRM.
> > > > This introduces a slight change in the original intel flow
> > > > as it splits the unique driver protocol from the generic implementation.
> > > > 
> > > > Patches 5-7 split the HDCP flow on the i915 driver to make use of the common DRM helpers.
> > > > 
> > > > Patches 8-10 implement HDCP on MSM driver.
> > > > 
> > > > Thanks,
> > > > -Mark Yacoub
> > > > 
> > > > Sean Paul (10):
> > > >     drm/hdcp: Add drm_hdcp_atomic_check()
> > > >     drm/hdcp: Avoid changing crtc state in hdcp atomic check
> > > >     drm/hdcp: Update property value on content type and user changes
> > > >     drm/hdcp: Expand HDCP helper library for enable/disable/check
> > > >     drm/i915/hdcp: Consolidate HDCP setup/state cache
> > > >     drm/i915/hdcp: Retain hdcp_capable return codes
> > > >     drm/i915/hdcp: Use HDCP helpers for i915
> > > >     dt-bindings: msm/dp: Add bindings for HDCP registers
> > > >     arm64: dts: qcom: sc7180: Add support for HDCP in dp-controller
> > > 
> > > Dear i915 maintainers,
> > > 
> > > I wanted to ping you regarding this patch series. If there are no comments
> > > for the series from you side, would it be possible to land Intel-specific
> > > and generic patches into drm-intel tree? We will continue working on the msm
> > > specific parts and merge them through the msm tree.
> > 
> > pushed to drm-intel-next.
> > 
> > should be propagated in a few weeks to drm-next on our next pull request.
> 
> Probably there is some kind of confusion here. You've pushed the DSC
> patches, while the response was sent to the HDCP series.

I'm sorry, my confusion for replying to the wrong thread.

So, on this one here I believe it would be helpful if there's a split
in the series with the already reviewed ones related to i915 are resent
separated from the rest, send with --subject-prefix="CI" so when that
pass CI we just merge it through drm-intel-next


> 
> -- 
> With best wishes
> Dmitry
> 

  reply	other threads:[~2023-05-22 12:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 15:43 [Intel-gfx] [PATCH v10 00/10] drm/hdcp: Pull HDCP auth/exchange/check into helpers Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 01/10] drm/hdcp: Add drm_hdcp_atomic_check() Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 02/10] drm/hdcp: Avoid changing crtc state in hdcp atomic check Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 03/10] drm/hdcp: Update property value on content type and user changes Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 04/10] drm/hdcp: Expand HDCP helper library for enable/disable/check Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 05/10] drm/i915/hdcp: Consolidate HDCP setup/state cache Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 06/10] drm/i915/hdcp: Retain hdcp_capable return codes Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 07/10] drm/i915/hdcp: Use HDCP helpers for i915 Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 08/10] dt-bindings: msm/dp: Add bindings for HDCP registers Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 09/10] arm64: dts: qcom: sc7180: Add support for HDCP in dp-controller Mark Yacoub
2023-04-19 15:43 ` [Intel-gfx] [PATCH v10 10/10] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers Mark Yacoub
2023-04-20  7:41   ` kernel test robot
2023-04-20 11:39   ` kernel test robot
2023-04-19 18:00 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/hdcp: Pull HDCP auth/exchange/check into helpers (rev10) Patchwork
2023-04-26 16:29 ` [Intel-gfx] [PATCH v10 00/10] drm/hdcp: Pull HDCP auth/exchange/check into helpers Doug Anderson
2023-04-27 15:51   ` Dmitry Baryshkov
2023-05-19 16:55 ` Dmitry Baryshkov
2023-05-19 21:16   ` Rodrigo Vivi
2023-05-19 23:07     ` Dmitry Baryshkov
2023-05-22 12:59       ` Rodrigo Vivi [this message]
2023-05-25 23:46         ` Doug Anderson

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=ZGtnH5YJ8u6bMo4j@rdvivi-mobl4 \
    --to=rodrigo.vivi@kernel.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=markyacoub@chromium.org \
    --cc=markyacoub@google.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=seanpaul@chromium.org \
    /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