All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: Richard Weinberger <richard@nod.at>,
	xenomai@lists.linux.dev, upstream@sigma-star.at,
	Jan Kiszka <jan.kiszka@siemens.com>
Cc: upstream+xenomai@sigma-star.at
Subject: Re: [PATCH] kernel: Clean up generated syscall_entries.h file
Date: Thu, 27 Jun 2024 10:20:34 +0200	[thread overview]
Message-ID: <3081086.VqyquhjGfd@somecomputer> (raw)
In-Reply-To: <33dbafe0-3da7-4065-bfa5-0fc7fe4432bf@siemens.com>

Am Donnerstag, 27. Juni 2024, 09:36:27 CEST schrieb Jan Kiszka:
> "Any target that utilizes if_changed must be listed in $(targets),
> otherwise the command line check will fail, and the target will
> always be built."

Yes, but why is if_changed needed at all?
syscall_entries is in the prerequisites list of $(obj)/syscall_entries.h.
 
> If you find a better pattern, that propose it - but test all the corner
> cases of required as well as unneeded rebuilding first.

The diff in my last mail should fulfill all that.
I removed if_changed and replaced it with cmd.

But let's stay on the safe side, I'll send a v2 for the syscall_entries.h
file and do more testing wrt. if_changed/target.

Thanks,
//richard

-- 
​​​​​sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT
UID/VAT Nr: ATU 66964118 | FN: 374287y



  reply	other threads:[~2024-06-27  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 19:26 [PATCH] kernel: Clean up generated syscall_entries.h file Richard Weinberger
2024-06-27  6:29 ` Jan Kiszka
2024-06-27  7:25   ` Richard Weinberger
2024-06-27  7:36     ` Jan Kiszka
2024-06-27  8:20       ` Richard Weinberger [this message]
2024-06-27 11:31         ` Jan Kiszka

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=3081086.VqyquhjGfd@somecomputer \
    --to=richard@sigma-star.at \
    --cc=jan.kiszka@siemens.com \
    --cc=richard@nod.at \
    --cc=upstream+xenomai@sigma-star.at \
    --cc=upstream@sigma-star.at \
    --cc=xenomai@lists.linux.dev \
    /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.