Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Ravi Kumar Vodapalli <ravi.kumar.vodapalli@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] Different platforms has different PAT encoding in PTE and PDE format, add correct PAT encoding for pre-Xe2 platforms (XELP, XEHPC, XELPG).
Date: Wed, 09 Aug 2023 10:54:50 -0700	[thread overview]
Message-ID: <87r0oc2j9x.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230809120730.383981-1-ravi.kumar.vodapalli@intel.com>

On Wed, 09 Aug 2023 05:07:30 -0700, Ravi Kumar Vodapalli wrote:
>
> Bspec: 45101, 71582
> Signed-off-by: Ravi Kumar Vodapalli <ravi.kumar.vodapalli@intel.com>

Why such a long patch title? Please use patch title and patch description
which fits in 75 chars per line (whatever checkpatch allows). Thanks.

  parent reply	other threads:[~2023-08-09 17:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 12:07 [Intel-xe] [PATCH] Different platforms has different PAT encoding in PTE and PDE format, add correct PAT encoding for pre-Xe2 platforms (XELP, XEHPC, XELPG) Ravi Kumar Vodapalli
2023-08-09 12:35 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-08-09 12:35 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-09 12:37 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-09 12:40 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-09 12:41 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-08-09 17:54 ` Dixit, Ashutosh [this message]
2023-08-09 18:26 ` [Intel-xe] [PATCH] " Lucas De Marchi
2023-08-11 20:30   ` Matt Roper
2023-08-11 20:38     ` Matthew Brost

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=87r0oc2j9x.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ravi.kumar.vodapalli@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