Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
	rodrigo.vivi@intel.com, matthew.d.roper@intel.com,
	intel-gfx@lists.freedesktop.org, anshuman.gupta@intel.com,
	badal.nilawar@intel.com, riana.tauro@intel.com
Subject: Re: [PATCH v4 0/4] Implement Wa_14022698537
Date: Thu, 12 Dec 2024 12:02:27 +0200	[thread overview]
Message-ID: <Z1q0s7ncARjeN8ZM@black.fi.intel.com> (raw)
In-Reply-To: <Z1qgcHImmUFB9SVi@ashyti-mobl2.lan>

On Thu, Dec 12, 2024 at 09:36:00AM +0100, Andi Shyti wrote:
> Hi Raag,
> 
> On Thu, Dec 12, 2024 at 05:22:32AM +0200, Raag Jadav wrote:
> > On Thu, Dec 12, 2024 at 12:40:07AM +0100, Andi Shyti wrote:
> > > > Raag Jadav (4):
> > > >   drm/intel/pciids: Refactor DG2 PCI IDs into segment ranges
> > > >   drm/i915/dg2: Introduce DG2_D subplatform
> > > >   drm/i915: Introduce intel_cpu_info.c for CPU IDs
> > > >   drm/i915/dg2: Implement Wa_14022698537
> > > 
> > > merged to drm-intel-next.
> > 
> > Thanks, appreciate it.
> > 
> > Andy usually picks the cover letter as well, we don't do that here?
> 
> what do you mean with taking the cover letter?
> 
> For pushing the patch I use the dim tool and I feed it with the
> cover letter's mbox file.

Ah okay. I think he uses b4 with cover letter as a merge patch. Kind of
like treating it as a PR. It's useful when we have a nice summary which
adds required context (which I understand is not the case here anyway).

Examples,

$ git show 563532b49aa0aa00
$ git show e4e17186723570e8

Raag

  reply	other threads:[~2024-12-12 10:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 11:59 [PATCH v4 0/4] Implement Wa_14022698537 Raag Jadav
2024-12-11 11:59 ` [PATCH v4 1/4] drm/intel/pciids: Refactor DG2 PCI IDs into segment ranges Raag Jadav
2024-12-11 11:59 ` [PATCH v4 2/4] drm/i915/dg2: Introduce DG2_D subplatform Raag Jadav
2024-12-11 11:59 ` [PATCH v4 3/4] drm/i915: Introduce intel_cpu_info.c for CPU IDs Raag Jadav
2024-12-11 11:59 ` [PATCH v4 4/4] drm/i915/dg2: Implement Wa_14022698537 Raag Jadav
2024-12-11 12:45 ` ✗ Fi.CI.CHECKPATCH: warning for Implement Wa_14022698537 (rev3) Patchwork
2024-12-11 12:45 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-12-11 12:59 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-11 14:13 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-11 23:40 ` [PATCH v4 0/4] Implement Wa_14022698537 Andi Shyti
2024-12-12  3:22   ` Raag Jadav
2024-12-12  8:35     ` Jani Nikula
2024-12-12  8:36     ` Andi Shyti
2024-12-12 10:02       ` Raag Jadav [this message]
2024-12-12 10:48         ` b4 Merge patch series (was: Re: [PATCH v4 0/4] Implement Wa_14022698537) Jani Nikula

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=Z1q0s7ncARjeN8ZM@black.fi.intel.com \
    --to=raag.jadav@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=riana.tauro@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox