intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
Subject: RE: [PATCH] drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro
Date: Mon, 29 Jul 2024 13:27:04 +0300	[thread overview]
Message-ID: <87sevsxzlz.fsf@intel.com> (raw)
In-Reply-To: <SN7PR11MB6750236145E4EFF483D6A593E3B72@SN7PR11MB6750.namprd11.prod.outlook.com>

On Mon, 29 Jul 2024, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> -----Original Message-----
>> From: Jani Nikula <jani.nikula@linux.intel.com>
>> Sent: Monday, July 29, 2024 3:26 PM
>> To: Kandpal, Suraj <suraj.kandpal@intel.com>; intel-
>> gfx@lists.freedesktop.org
>> Cc: Nautiyal, Ankit K <ankit.k.nautiyal@intel.com>; Kandpal, Suraj
>> <suraj.kandpal@intel.com>
>> Subject: Re: [PATCH] drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro
>> 
>> On Mon, 29 Jul 2024, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
>> > Fix HDCP2_STREAM_STATUS macro, it called pipe instead of port never
>> > threw a compile error as no one used it.
>> 
>> Fixes: ?
>> 
>
> Anyway to find it,
> Did a git blame but since one of your patches separated intel_hdcp_regs.h from i915_regs.h
> All I can see is your commit which I don't think is the correct commit to add.

Please just dig deeper. git blaming through refactoring is an essential
skill.

BR,
Jani.



>
> Regards,
> Suraj Kandpal
>
>> >
>> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>> > ---
>> >  drivers/gpu/drm/i915/display/intel_hdcp_regs.h | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/gpu/drm/i915/display/intel_hdcp_regs.h
>> > b/drivers/gpu/drm/i915/display/intel_hdcp_regs.h
>> > index a568a457e532..f590d7f48ba7 100644
>> > --- a/drivers/gpu/drm/i915/display/intel_hdcp_regs.h
>> > +++ b/drivers/gpu/drm/i915/display/intel_hdcp_regs.h
>> > @@ -251,7 +251,7 @@
>> >  #define HDCP2_STREAM_STATUS(dev_priv, trans, port) \
>> >  					(TRANS_HDCP(dev_priv) ? \
>> >
>> TRANS_HDCP2_STREAM_STATUS(trans) : \
>> > -					 PIPE_HDCP2_STREAM_STATUS(pipe))
>> > +					 PIPE_HDCP2_STREAM_STATUS(port))
>> >
>> >  #define _PORTA_HDCP2_AUTH_STREAM		0x66F00
>> >  #define _PORTB_HDCP2_AUTH_STREAM		0x66F04
>> 
>> --
>> Jani Nikula, Intel

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-07-29 10:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29  4:08 [PATCH] drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro Suraj Kandpal
2024-07-29  4:43 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-07-29  6:29 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-07-29  9:56 ` [PATCH] " Jani Nikula
2024-07-29 10:19   ` Kandpal, Suraj
2024-07-29 10:27     ` Jani Nikula [this message]
2024-07-30  3:55 ` Suraj Kandpal
2024-07-30  8:00   ` Jani Nikula
2024-07-30  4:38 ` ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (rev2) Patchwork
2024-07-30  8:10 ` ✓ Fi.CI.BAT: success " Patchwork
2024-07-30 15:00 ` ✗ Fi.CI.IGT: failure " Patchwork

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=87sevsxzlz.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=suraj.kandpal@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).