All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Calvin Owens <calvin@wbinvd.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"airlied@gmail.com" <airlied@gmail.com>,
	"lucas.demarchi@intel.com" <lucas.demarchi@intel.com>,
	"thomas.hellstrom@linux.intel.com"
	<thomas.hellstrom@linux.intel.com>,
	"simona@ffwll.ch" <simona@ffwll.ch>
Subject: Re: [PATCH] drm/xe: Don't use absolute path in generated header comment
Date: Tue, 23 Dec 2025 10:06:40 -0500	[thread overview]
Message-ID: <aUqwANs-HdhISQ5Z@intel.com> (raw)
In-Reply-To: <aUmpZzD_5RauueUo@mozart.vkv.me>

On Mon, Dec 22, 2025 at 12:26:15PM -0800, Calvin Owens wrote:
> On Monday 12/22 at 16:56 +0000, Vivi, Rodrigo wrote:
> > On Sun, 2025-12-21 at 11:53 -0800, Calvin Owens wrote:
> > > On Friday 10/31 at 07:48 -0700, Calvin Owens wrote:
> > > > Building the XE driver through Yocto throws this QA warning:
> > > > 
> > > >     WARNING: mc:house:linux-stable-6.17-r0 do_package_qa: QA Issue:
> > > > File /usr/src/debug/linux-
> > > > stable/6.17/drivers/gpu/drm/xe/generated/xe_device_wa_oob.h in
> > > > package linux-stable-src contains reference to TMPDIR [buildpaths]
> > > >     WARNING: mc:house:linux-stable-6.17-r0 do_package_qa: QA Issue:
> > > > File /usr/src/debug/linux-
> > > > stable/6.17/drivers/gpu/drm/xe/generated/xe_wa_oob.h in package
> > > > linux-stable-src contains reference to TMPDIR [buildpaths]
> > > > 
> > > > ...because the comment at the top of the generated header contains
> > > > the
> > > > absolute path to the rules file at build time:
> > > > 
> > > >     * This file was generated from rules: /home/calvinow/git/meta-
> > > > house/build/tmp-house/work-shared/nuc14rvhu7/kernel-
> > > > source/drivers/gpu/drm/xe/xe_device_wa_oob.rules
> > > > 
> > > > Fix this minor annoyance by putting the basename of the rules file
> > > > in
> > > > the generated comment instead of the absolute path, so the
> > > > generated
> > > > header contents no longer depend on the location of the kernel
> > > > source.
> > > 
> > > Hi all,
> > > 
> > > This is about as trivial as it gets: it's been a couple months, can I
> > > get some eyes on this please?
> > > 
> > > This is the only place in the entire kernel source where the content
> > > of
> > > a generated header depends on the absolute path to the kernel tree.
> > > It
> > > makes kernel source packages non-reproducible.
> > 
> > Sorry about that and for the delay.
> > 
> > I just resent the patch for CI:
> > https://lore.kernel.org/intel-xe/20251222165441.516102-2-rodrigo.vivi@intel.com/
> > 
> > We can push after passing it.
> 
> No apology necessary, thanks for kicking it for me :)

Patch pushed to drm-xe-next

> 
> Calvin
> 
> > Thanks,
> > Rodrigo.
> > 
> > > 
> > > Thanks
> > > Calvin
> > > 
> > > > Signed-off-by: Calvin Owens <calvin@wbinvd.org>
> > > > ---
> > > >  drivers/gpu/drm/xe/xe_gen_wa_oob.c | 3 ++-
> > > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > > 
> > > > diff --git a/drivers/gpu/drm/xe/xe_gen_wa_oob.c
> > > > b/drivers/gpu/drm/xe/xe_gen_wa_oob.c
> > > > index 247e41c1c48d..e7a50b1348b7 100644
> > > > --- a/drivers/gpu/drm/xe/xe_gen_wa_oob.c
> > > > +++ b/drivers/gpu/drm/xe/xe_gen_wa_oob.c
> > > > @@ -195,7 +195,8 @@ int main(int argc, const char *argv[])
> > > >  		}
> > > >  	}
> > > >  
> > > > -	fprintf(args[ARGS_CHEADER].f, HEADER, args[ARGS_INPUT].fn,
> > > > prefix, prefix);
> > > > +	fprintf(args[ARGS_CHEADER].f, HEADER,
> > > > xbasename(args[ARGS_INPUT].fn),
> > > > +		prefix, prefix);
> > > >  
> > > >  	ret = parse(args[ARGS_INPUT].f, args[ARGS_CSOURCE].f,
> > > >  		    args[ARGS_CHEADER].f, prefix);
> > > > -- 
> > > > 2.47.3
> > > > 

      reply	other threads:[~2025-12-23 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 14:48 [PATCH] drm/xe: Don't use absolute path in generated header comment Calvin Owens
2025-11-03 13:20 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2025-11-16 16:12   ` Calvin Owens
2025-12-21 19:53 ` [PATCH] " Calvin Owens
2025-12-22 16:56   ` Vivi, Rodrigo
2025-12-22 20:26     ` Calvin Owens
2025-12-23 15:06       ` Rodrigo Vivi [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=aUqwANs-HdhISQ5Z@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=calvin@wbinvd.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@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 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.