All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	intel-xe@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [Intel-xe] [PATCH] fixup! drm/xe/display: Add intel_pps support too
Date: Fri, 12 May 2023 10:01:05 -0400	[thread overview]
Message-ID: <ZF5GoZIRfdHPg+2w@rdvivi-mobl4> (raw)
In-Reply-To: <87mt2bkpye.fsf@intel.com>

On Thu, May 11, 2023 at 03:33:29PM +0300, Jani Nikula wrote:
> On Wed, 10 May 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> > On Wed, May 10, 2023 at 07:02:20PM +0300, Jani Nikula wrote:
> >>This is an unrelated, unneeded change in "drm/xe/display: Add intel_pps
> >>support too".
> >>
> >>After that gets applied, "drm/xe/display: Add intel_pps support too"
> >>should itself be a fixup to "drm/xe/display: Implement display support".
> >>
> >>Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >
> >
> > Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
> 
> Thanks, pushed to drm-xe-next.
> 
> Rodrigo, what would be the best way to add a git rebase todo list for
> you?

An email here is fine.

I'm going to run a git rebase clean-up today or next monday.

what do I need to do besides taking care of the fixup and remove the dummy
commits?

(my only rule is that the rebase clean-up git diff HEAD..origin/drm-xe-next needs to come empty)

> 
> 
> BR,
> Jani.
> 
> 
> >
> > Lucas De Marchi
> >
> >>---
> >> drivers/gpu/drm/i915/display/intel_pps.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >>diff --git a/drivers/gpu/drm/i915/display/intel_pps.c b/drivers/gpu/drm/i915/display/intel_pps.c
> >>index cfe40c64f6d4..c859b066e827 100644
> >>--- a/drivers/gpu/drm/i915/display/intel_pps.c
> >>+++ b/drivers/gpu/drm/i915/display/intel_pps.c
> >>@@ -481,7 +481,7 @@ static void intel_pps_get_registers(struct intel_dp *intel_dp,
> >> 				    struct pps_registers *regs)
> >> {
> >> 	struct drm_i915_private *dev_priv = dp_to_i915(intel_dp);
> >>-	int pps_idx = 0;
> >>+	int pps_idx;
> >>
> >> 	memset(regs, 0, sizeof(*regs));
> >>
> >>-- 
> >>2.39.2
> >>
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-05-12 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 16:02 [Intel-xe] [PATCH] fixup! drm/xe/display: Add intel_pps support too Jani Nikula
2023-05-10 17:08 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-05-10 17:10 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-10 17:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-10 17:38 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-05-10 20:20 ` [Intel-xe] [PATCH] " Lucas De Marchi
2023-05-11 12:33   ` Jani Nikula
2023-05-12 14:01     ` Rodrigo Vivi [this message]
2023-05-12 18:07       ` Lucas De Marchi

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=ZF5GoZIRfdHPg+2w@rdvivi-mobl4 \
    --to=rodrigo.vivi@kernel.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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 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.