From: Riana Tauro <riana.tauro@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<aravind.iddamsetty@linux.intel.com>, <anshuman.gupta@intel.com>,
<joonas.lahtinen@linux.intel.com>, <simona.vetter@ffwll.ch>,
<airlied@gmail.com>, <pratik.bari@intel.com>,
<joshua.santosh.ranjan@intel.com>,
<ashwin.kumar.kulkarni@intel.com>, <shubham.kumar@intel.com>,
<ravi.kishore.koppuravuri@intel.com>, <raag.jadav@intel.com>,
<anvesh.bakwad@intel.com>,
Zack McKevitt <zachary.mckevitt@oss.qualcomm.com>,
Lijo Lazar <lijo.lazar@amd.com>,
"Hawking Zhang" <Hawking.Zhang@amd.com>,
"David S. Miller" <davem@davemloft.net>,
"Paolo Abeni" <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v8 1/5] drm/ras: Introduce the DRM RAS infrastructure over generic netlink
Date: Sat, 28 Feb 2026 12:14:24 +0530 [thread overview]
Message-ID: <43a08974-fb35-47a5-b77d-f14e284aea98@intel.com> (raw)
In-Reply-To: <20260226070509.2c7346b3@kernel.org>
On 2/26/2026 8:35 PM, Jakub Kicinski wrote:
> On Thu, 26 Feb 2026 15:17:55 +0530 Riana Tauro wrote:
>>> Oh interesting.. that's technically supported but the regen script
>>> uses "-o $file --cmp-out" instead of "> $file". If we were to use
>>> a shell redirect we override the file each time which makes incremental
>>> kernel builds much larger.
>>
>> If i am using this for the first time (not every time). Shouldn't it
>> include the header file (#include "drm_ras_nl.h) too?
>>
>> tools/net/ynl/pyynl/ynl_gen_c.py --spec
>> Documentation/netlink/specs/drm_ras.yaml --mode kernel --source
>>
>> But i am seeing this include only when i regenerate using ynl-regen.sh.
>> Is it mandatory to regenerate after the initial use of the above command.
>>
>>>
>>>> I used above commands to generate the initial files moving the
>>>> drm_ras_nl.h from include/ to drm layer.
>>>>
>>>> Even after that if i regen using tools/net/ynl/ynl-regen.sh -f
>>>> I see the above diff.
>>>>
>>>> Am i using the commands wrong or missing something?
>>>
>>> If you use the redirect the script doesn't know what the file name is
>>> so it gives up on adding the local header. If you really want to have
>>> the header under include we can just add an option for "--no-auto-hdr"
>>
>> No its not necessary to be in the include directory as it is used
>> internally by drm code. @Rodrigo I will move this since this is used
>> only by drm_ras.c
>>
>> But even after i move it to drivers/gpu/drm/. The initial generation
>> using ynl_gen_c.py doesn't include this header even if the header was
>> generated first.
>>
>> The header is included only when i use ynl-regen. Is that expected?
>
> As I explained above you should use the -o $file argument rather than
> a redirect of stdout.
This worked. Thanks a lot for the suggestion
I had tried this approach but i must have made some other mistake.
Maybe i tried with the existing file.
Thank you
Riana
prev parent reply other threads:[~2026-02-28 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260223060541.526397-7-riana.tauro@intel.com>
2026-02-23 6:05 ` [PATCH v8 1/5] drm/ras: Introduce the DRM RAS infrastructure over generic netlink Riana Tauro
2026-02-25 0:22 ` Jakub Kicinski
2026-02-25 6:08 ` Riana Tauro
2026-02-26 0:18 ` Jakub Kicinski
2026-02-26 9:47 ` Riana Tauro
2026-02-26 15:05 ` Jakub Kicinski
2026-02-28 6:44 ` Riana Tauro [this message]
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=43a08974-fb35-47a5-b77d-f14e284aea98@intel.com \
--to=riana.tauro@intel.com \
--cc=Hawking.Zhang@amd.com \
--cc=airlied@gmail.com \
--cc=anshuman.gupta@intel.com \
--cc=anvesh.bakwad@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=ashwin.kumar.kulkarni@intel.com \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@google.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=joshua.santosh.ranjan@intel.com \
--cc=kuba@kernel.org \
--cc=lijo.lazar@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pratik.bari@intel.com \
--cc=raag.jadav@intel.com \
--cc=ravi.kishore.koppuravuri@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=shubham.kumar@intel.com \
--cc=simona.vetter@ffwll.ch \
--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