mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Masahiro Yamada" <masahiroy@kernel.org>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-kbuild@vger.kernel.org,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nicolas@fjasle.eu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: mark "FORCE" target as secondary
Date: Wed, 17 Jul 2024 20:50:23 +0200	[thread overview]
Message-ID: <41f36e68-ff7e-468d-a110-46895ac3a5c7@app.fastmail.com> (raw)
In-Reply-To: <CAK7LNASYnPNsJraL1qv+MFviTnPxjmc2Dmd7EcvJRCNLtHfZ6Q@mail.gmail.com>

On Wed, Jul 17, 2024, at 18:45, Masahiro Yamada wrote:
>> On Wed, Jul 17, 2024, at 17:18, Masahiro Yamada wrote:
>>
>> Should we maybe revert ff96f5c6971c..3db80c999deb then
>> and find a better way to do it in 6.12?
>
> I do not think so.
>
> I pretty much like 4fe53bf2ba0a45cd708dcd4c3e8e1950731b3d4d,
> and I believe generating all syscall headers from a table
> is the right thing to do.
> So, it must happen.

Right, I meant to leave that part here and just revert
the Makefile changes until we have something that has
seen enough testing.

> Currently, the new syscall-y syntax can be used only for
> architectures using the generic syscall table.
> I wonder what we should do for the other legacy architectures.

I have patches for all architectures at

https://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git/log/?h=syscall-tbl-6.11&id=92499ba526eac435

but I stopped after the ones using the generic syscall
table since I had spent more time making sure the actual
table contents are unchanged.

> For the rebuild problem, I think this should work:
> https://lore.kernel.org/all/20240717162421.1402773-1-masahiroy@kernel.org/T/#u
>
> (I only compile-tested arch64 and riscv, but the other architectires
> should be the same pattern.)

Right, I completely missed the "existing-targets" bit, and
without that I couldn't figure out the rest correctly.

I have checked this on the other architectures now and
tried out the bit with the changed command line I got
wrong.

Sorry for causing these problems and thanks a lot for
the fix!

     Arnd

      reply	other threads:[~2024-07-17 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 12:42 Arnd Bergmann
2024-07-17 15:18 ` Masahiro Yamada
2024-07-17 16:24   ` Arnd Bergmann
2024-07-17 16:45     ` Masahiro Yamada
2024-07-17 18:50       ` Arnd Bergmann [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=41f36e68-ff7e-468d-a110-46895ac3a5c7@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®