public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Summers, Stuart" <stuart.summers@intel.com>,
	"Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Lin, Shuicheng" <shuicheng.lin@intel.com>,
	"Yang, Fei" <fei.yang@intel.com>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>,
	"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH] drm/xe/guc: Add support for NPK as a GuC log target
Date: Wed, 08 Apr 2026 16:18:40 +0300	[thread overview]
Message-ID: <07168815102825e019bfd6eb7ad9b82dd0040953@intel.com> (raw)
In-Reply-To: <4c38349fdee090e69100437781c3f5cc2a354b4c.camel@intel.com>

On Tue, 07 Apr 2026, "Summers, Stuart" <stuart.summers@intel.com> wrote:
> On Tue, 2026-04-07 at 11:48 +0200, Michal Wajdeczko wrote:
>> 
>> On 4/7/2026 12:53 AM, Stuart Summers wrote:
>> > From: John Harrison <John.C.Harrison@Intel.com>
>> > 
>> > GuC provides the ability to gather logs through a hardware
>> > interface
>> > called NPK. For certain debugging scenarios this can be
>> > advantageous
>> > over getting logs from memory (or in addition to).
>> > 
>> > Add a hook for this alternate debugging mode via a configfs. This
>> > translates into a parameter passed to GuC during load time.
>> > 
>> > v2: Convert to configfs from modparam (Matt)
>> > v3: Configfs documentation formatting (Shuicheng)
>> >     Kerneldoc/comment add + configfs entry ordering
>> >     Only set the guc_log_target when GuC log is enabled (Daniele)
>> 
>> nit: we may keep change log under --- so it stays on the ML only
>
> Ok makes sense I'll do that on the next upload.

Is this an intentional deviation from the quite prevalent drm subsystem
style of including the changelog in the commit message?

I'm not dead set on either style personally, but I do not like
conflicting review feedback, and people not knowing what to do.


BR,
Jani.


-- 
Jani Nikula, Intel

  parent reply	other threads:[~2026-04-08 13:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 22:53 [PATCH] drm/xe/guc: Add support for NPK as a GuC log target Stuart Summers
2026-04-06 23:00 ` ✓ CI.KUnit: success for drm/xe/guc: Add support for NPK as a GuC log target (rev3) Patchwork
2026-04-06 23:46 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-07  3:29 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-07  9:48 ` [PATCH] drm/xe/guc: Add support for NPK as a GuC log target Michal Wajdeczko
2026-04-07 18:55   ` Summers, Stuart
2026-04-08 12:40     ` Michal Wajdeczko
2026-04-08 21:51       ` Summers, Stuart
2026-04-08 13:18     ` Jani Nikula [this message]
2026-04-08 22:02       ` Summers, Stuart
  -- strict thread matches above, loose matches on Subject: below --
2026-02-26 23:26 Stuart Summers
2026-03-19 18:25 ` Summers, Stuart
2026-04-06 17:58   ` Summers, Stuart
2026-04-06 21:28 ` Daniele Ceraolo Spurio
2026-04-06 22:37   ` Summers, Stuart
2026-04-06 23:45     ` Daniele Ceraolo Spurio
2026-04-06 23:59       ` Summers, Stuart
2026-04-06 21:59 ` Lin, Shuicheng
2026-04-06 22:38   ` Summers, Stuart
2026-02-24 20:36 Stuart Summers
2026-02-25  0:24 ` Matt Roper
2026-02-25 21:52   ` Summers, Stuart
2026-02-25 22:46     ` Matt Roper

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=07168815102825e019bfd6eb7ad9b82dd0040953@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=Michal.Wajdeczko@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=fei.yang@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=shuicheng.lin@intel.com \
    --cc=stuart.summers@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