From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: igt-dev@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] xe_live_ktest: Use xe_live_test kernel module
Date: Mon, 15 Jan 2024 09:21:35 +0200 [thread overview]
Message-ID: <87mst7rri8.fsf@intel.com> (raw)
In-Reply-To: <11e1b3f4-b0ba-4095-96c6-f2bf18f27fd2@linux.intel.com>
On Mon, 15 Jan 2024, Mauro Carvalho Chehab <mauro.chehab@linux.intel.com> wrote:
> On 1/12/24 15:29, Lucas De Marchi wrote:
>>> On such case, you should document kunit_debugfs at Documentation/ABI.
>>
>> debugfs is not part of ABI.
>
> That's arguable. Check Documentation/ABI and you'll see several debugfs
> nodes documented there.
I guess you could argue documenting your debugfs under Documentation/ABI
makes it ABI, but I'd avoid doing that. Usually we use debugfs precisely
to avoid the burden of ABI and all the baggage that brings.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-15 7:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 22:49 [igt-dev] [PATCH i-g-t] xe_live_ktest: Use xe_live_test kernel module Lucas De Marchi
2023-12-06 0:04 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-12-06 2:30 ` [igt-dev] ✗ CI.xeBAT: " Patchwork
2023-12-07 15:41 ` [igt-dev] [PATCH i-g-t] " Mauro Carvalho Chehab
[not found] ` <3kunqgqyf7tobiwhcpvjp7rcvidrgnz2jq3qqoxjbl7kaftdq7@7hdweo57htff>
[not found] ` <njwvai6cu7jwmy7lmg3vkg4jd52uq2f6es4obvdplkz43i6hpe@jqrzk4bveqqc>
2024-01-11 23:45 ` Lucas De Marchi
2024-01-12 8:32 ` Mauro Carvalho Chehab
2024-01-12 14:29 ` Lucas De Marchi
2024-01-15 7:08 ` Mauro Carvalho Chehab
2024-01-15 7:21 ` Jani Nikula [this message]
2024-01-15 19:52 ` Mauro Carvalho Chehab
2024-01-16 14:50 ` Lucas De Marchi
2024-01-17 6:14 ` Mauro Carvalho Chehab
2024-01-22 11:35 ` Janusz Krzysztofik
2024-01-22 15:37 ` Lucas De Marchi
2024-01-23 11:18 ` Janusz Krzysztofik
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=87mst7rri8.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=mauro.chehab@linux.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