Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Violet Monti <violet.monti@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Matt Atwood <matthew.s.atwood@intel.com>
Subject: Re: [PATCH] drm/xe/ptl: Add a new PTL PCI ID
Date: Thu, 1 Oct 2026 08:41:47 -0400	[thread overview]
Message-ID: <ar5VC6_a7lqYHUQe@intel.com> (raw)
In-Reply-To: <arcahvIqBmCytAmw@intel.com>

On Fri, Sep 25, 2026 at 09:06:14PM -0400, Rodrigo Vivi wrote:
> On Wed, Sep 23, 2026 at 10:11:05AM -0700, Violet Monti wrote:
> > On Tue, Sep 22, 2026 at 06:21:21PM -0400, Rodrigo Vivi wrote:
> > > On Tue, Sep 22, 2026 at 09:56:08AM -0700, Violet Monti wrote:
> > > > A new PCI ID for PTL.
> > > > 
> > > > Bspec: 72574
> > > > 
> > > > Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
> > > > Signed-off-by: Violet Monti <violet.monti@intel.com>
> > > 
> > > I honestly believe it would be better and faster if you had just reviewed
> > > the version that Matt sent yesterday instead of resending it.
> > 
> > The reason for my resubmission was to rerun the CI results after a KUnit
> > failure unrelated to the PCI ID change. Matt is out for this week, and
> > delegated this patch to me to review and handle in his absence. Since I
> > am not the owner of the original submission, I was not able to rerun the
> > tests using the resubmit.
> > 
> > Is there a preferred method for re-testing patches that have been
> > delegated, such as situations like this?
> 
> 
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> and pushed. Thanks for the patch and diligence.

Matt, please accept my apologies, but I just noticed that I pushed the patch
with the wrong authorship.

Violet, next time you are handling someone's else patch you sign it off, but
never ever change the authorship of it if you haven't modified the content.

> 
> > 
> > Violet
> > > 
> > > > ---
> > > >  include/drm/intel/pciids.h | 1 +
> > > >  1 file changed, 1 insertion(+)
> > > > 
> > > > diff --git a/include/drm/intel/pciids.h b/include/drm/intel/pciids.h
> > > > index dff389b56eb3..32c88a690ad8 100644
> > > > --- a/include/drm/intel/pciids.h
> > > > +++ b/include/drm/intel/pciids.h
> > > > @@ -880,6 +880,7 @@
> > > >  	MACRO__(0xB08F, ## __VA_ARGS__), \
> > > >  	MACRO__(0xB090, ## __VA_ARGS__), \
> > > >  	MACRO__(0xB0A0, ## __VA_ARGS__), \
> > > > +	MACRO__(0xB0A1, ## __VA_ARGS__), \
> > > >  	MACRO__(0xB0B0, ## __VA_ARGS__)
> > > >  
> > > >  /* WCL */
> > > > -- 
> > > > 2.43.0
> > > > 

  reply	other threads:[~2026-10-01 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 16:56 [PATCH] drm/xe/ptl: Add a new PTL PCI ID Violet Monti
2026-09-22 17:39 ` ✓ CI.KUnit: success for drm/xe/ptl: Add a new PTL PCI ID (rev2) Patchwork
2026-09-22 19:51 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-22 22:21 ` [PATCH] drm/xe/ptl: Add a new PTL PCI ID Rodrigo Vivi
2026-09-23 17:11   ` Violet Monti
2026-09-26  1:06     ` Rodrigo Vivi
2026-10-01 12:41       ` Rodrigo Vivi [this message]
2026-10-01 12:48         ` Rodrigo Vivi
2026-09-23  5:58 ` ✗ Xe.CI.FULL: failure for drm/xe/ptl: Add a new PTL PCI ID (rev2) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2026-09-18 18:19 [PATCH] drm/xe/ptl: Add a new PTL PCI ID Matt Atwood

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=ar5VC6_a7lqYHUQe@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.s.atwood@intel.com \
    --cc=violet.monti@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