From: Jani Nikula <jani.nikula@intel.com>
To: "Koppuravuri, Ravi Kishore" <ravi.kishore.koppuravuri@intel.com>,
igt-dev@lists.freedesktop.org
Cc: riana.tauro@intel.com, anshuman.gupta@intel.com,
mallesh.koujalagi@intel.com, raag.jadav@intel.com,
soham.purkait@intel.com
Subject: Re: [PATCH v3 03/10] lib/igt_drm_netlink: Introduce DRM RAS Netlink interface library
Date: Mon, 31 Aug 2026 15:33:03 +0300 [thread overview]
Message-ID: <a5e6c6f48cca679ef182b533cfd33079e20f5522@intel.com> (raw)
In-Reply-To: <19d17250-946f-46dc-a640-44ed08aa6dde@intel.com>
On Mon, 31 Aug 2026, "Koppuravuri, Ravi Kishore" <ravi.kishore.koppuravuri@intel.com> wrote:
> On 31-08-2026 14:16, Jani Nikula wrote:
>> On Mon, 24 Aug 2026, Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com> wrote:
>>> +struct app_context {
>> Why doesn't the name indicate netlink in any way?z
> I am using this structure to maintain the context of request received
> for the library functions and responses received from netlink functions.
> So I have not included netlink or nl for this structure name.
"struct app_context" in code seems too generic. If you see that alone,
you have no idea what it's related to.
I don't know, I guess I would've named it struct
igt_drm_netlink_<something>.
>>
>>> + struct nl_sock *sock;
>>> + int family_id;
>>> +};
>>> +
>>> +void igt_cleanup_nl_socket(struct app_context *ctx);
>>> +int igt_init_nl_socket(struct app_context *ctx);
>> IMO "nl" is the wrong place to abbreviate.
> libnl is the user space library used to communicate with DRM netlink
> socket in the kernel. All libnl API references have the word "nl" for
> netlink. So, I have followed the same in my library functions as well.
> Could you pls elaborate your suggestion, if am missing anything here.
I guess I would've named them igt_drm_netlink_{init,cleanup}().
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-08-31 12:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 16:41 [PATCH v3 00/10] Xe3P GPU Error Injection Test Suite with DRM RAS Netlink Support Ravi Kishore Koppuravuri
2026-08-24 16:41 ` [PATCH v3 01/10] drm-uapi/drm_ras: Add DRM RAS UAPI header Ravi Kishore Koppuravuri
2026-08-31 8:43 ` Jani Nikula
2026-08-24 16:41 ` [PATCH v3 02/10] lib/meson: Add libnl dependencies for DRM RAS support Ravi Kishore Koppuravuri
2026-08-24 16:41 ` [PATCH v3 03/10] lib/igt_drm_netlink: Introduce DRM RAS Netlink interface library Ravi Kishore Koppuravuri
2026-08-31 8:46 ` Jani Nikula
2026-08-31 11:30 ` Koppuravuri, Ravi Kishore
2026-08-31 12:33 ` Jani Nikula [this message]
2026-08-24 16:41 ` [PATCH v3 04/10] lib/igt_drm_netlink: add get_error_counter support Ravi Kishore Koppuravuri
2026-08-31 8:48 ` Jani Nikula
2026-08-31 11:23 ` Koppuravuri, Ravi Kishore
2026-08-31 12:38 ` Jani Nikula
2026-08-31 15:58 ` Purkait, Soham
2026-08-24 16:41 ` [PATCH v3 05/10] lib/igt_drm_netlink: add get_error_threshold command support Ravi Kishore Koppuravuri
2026-08-24 16:41 ` [PATCH v3 06/10] lib/igt_drm_netlink: add set_error_threshold " Ravi Kishore Koppuravuri
2026-08-24 16:41 ` [PATCH v3 07/10] tests/intel/xe_err_injection: Add GT UC Unicast GAM Walker Command Parity Error Injection Ravi Kishore Koppuravuri
2026-08-26 9:18 ` Purkait, Soham
2026-08-26 13:33 ` Koppuravuri, Ravi Kishore
2026-08-28 3:26 ` Harish Chegondi
2026-08-31 8:02 ` Purkait, Soham
2026-08-24 16:41 ` [PATCH v3 08/10] lib/igt_drm_netlink: add event notify subscription and event wait support Ravi Kishore Koppuravuri
2026-08-24 16:41 ` [PATCH v3 09/10] tests/intel/xe_err_injection: Add tests for L2 bank Corr err threshold scenarios Ravi Kishore Koppuravuri
2026-08-24 16:41 ` [PATCH v3 10/10] tests/intel/xe_err_injection: add CRI GPU requirement check Ravi Kishore Koppuravuri
2026-08-27 20:22 ` [PATCH v3 00/10] Xe3P GPU Error Injection Test Suite with DRM RAS Netlink Support Harish Chegondi
2026-08-28 4:03 ` Koppuravuri, Ravi Kishore
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=a5e6c6f48cca679ef182b533cfd33079e20f5522@intel.com \
--to=jani.nikula@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=ravi.kishore.koppuravuri@intel.com \
--cc=riana.tauro@intel.com \
--cc=soham.purkait@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.