From: Jakub Kicinski <kuba@kernel.org>
To: Zack McKevitt <zachary.mckevitt@oss.qualcomm.com>
Cc: dri-devel@lists.freedesktop.org, netdev@vger.kernel.org,
riana.tauro@intel.com, aravind.iddamsetty@linux.intel.com,
rodrigo.vivi@intel.com, raag.jadav@intel.com,
simona.vetter@ffwll.ch, airlied@gmail.com, ogabbay@kernel.org,
lizhi.hou@amd.com, karol.wachowski@linux.intel.com,
jeff.hugo@oss.qualcomm.com, carl.vanderlip@oss.qualcomm.com,
troy.hanson@oss.qualcomm.com,
youssef.abdulrahman@oss.qualcomm.com
Subject: Re: [PATCH 2/3] drm/drm_ras: Extend DRM RAS interface to include telemetry nodes
Date: Fri, 16 Oct 2026 18:07:14 -0700 [thread overview]
Message-ID: <20261016180714.05fc93c5@kernel.org> (raw)
In-Reply-To: <20261009173152.2436195-3-zachary.mckevitt@oss.qualcomm.com>
On Fri, 9 Oct 2026 10:31:51 -0700 Zack McKevitt wrote:
> + type: u64
prefer uint and then no pad
next prev parent reply other threads:[~2026-10-17 1:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 17:31 [PATCH 0/3] Extend drm_ras for qaic telemetry Zack McKevitt
2026-10-09 17:31 ` [PATCH 1/3] drm/drm_ras: Remove admin-perm flag from list-nodes operation Zack McKevitt
2026-10-14 21:11 ` Rodrigo Vivi
2026-10-09 17:31 ` [PATCH 2/3] drm/drm_ras: Extend DRM RAS interface to include telemetry nodes Zack McKevitt
2026-10-14 21:11 ` Rodrigo Vivi
2026-10-16 20:09 ` Zack McKevitt
2026-10-16 21:32 ` Rodrigo Vivi
2026-10-17 1:07 ` Jakub Kicinski [this message]
2026-10-09 17:31 ` [PATCH 3/3] accel/qaic: Add callbacks for DRM RAS netlink telemetry Zack McKevitt
2026-10-10 9:42 ` [syzbot ci] Re: Extend drm_ras for qaic telemetry syzbot ci
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=20261016180714.05fc93c5@kernel.org \
--to=kuba@kernel.org \
--cc=airlied@gmail.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=carl.vanderlip@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=karol.wachowski@linux.intel.com \
--cc=lizhi.hou@amd.com \
--cc=netdev@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=troy.hanson@oss.qualcomm.com \
--cc=youssef.abdulrahman@oss.qualcomm.com \
--cc=zachary.mckevitt@oss.qualcomm.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;
as well as URLs for NNTP newsgroup(s).