All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [kconfig][RFC] getting things like CONFIG_ARCH_HAS_SYSCALL_WRAPPER without bothering with selects
Date: Tue, 9 Aug 2022 16:52:28 -0700	[thread overview]
Message-ID: <CAHk-=wju2oRhU16tqgs5hD3GfF6sHBLZu-ihtnpmTiRyxO=Zqw@mail.gmail.com> (raw)
In-Reply-To: <YvLmPl8sgR2q3WgE@ZenIV>

On Tue, Aug 9, 2022 at 3:57 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> However, kconfig could do (1) without selects - something like
> bool ARCH_HAS_BAR_H
>         def_bool $(header-exists,bar.h)
>
> Does anybody see problems with the patch below?

I like the concept, but I'm not entirely sure how generic it is. How
many of those "arch has this header" do we really end up having?

Just looking at some of the "ARCH_HAS_XYZ" options, very few strike me
as being about a header file existing.

I'm not saying you picked the _only_ such case, but it doesn't seem
_entirely_ impossible that you did..

Looking at some of the other cases, they might be more interested in
not "does it have a header file", but "can I grep for this symbol
name"?

And that kind of "do you expose symbol XYZ in header ABC" query might
work for this ARCH_HAS_SYSCALL_WRAPPER case too?

So that seems like it might potentially be a more general-purpose
Kconfig helper. Hmm?

                    Linus

  reply	other threads:[~2022-08-09 23:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 22:57 [kconfig][RFC] getting things like CONFIG_ARCH_HAS_SYSCALL_WRAPPER without bothering with selects Al Viro
2022-08-09 23:52 ` Linus Torvalds [this message]
2022-08-10  2:31 ` Masahiro Yamada

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='CAHk-=wju2oRhU16tqgs5hD3GfF6sHBLZu-ihtnpmTiRyxO=Zqw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.