From: Sam Ravnborg <sam@ravnborg.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH 2/3] kbuild: generate asm-generic wrappers if mandatory headers are missing
Date: Thu, 6 Dec 2018 19:04:59 +0100 [thread overview]
Message-ID: <20181206180459.GA19166@ravnborg.org> (raw)
In-Reply-To: <1544009286-15705-2-git-send-email-yamada.masahiro@socionext.com>
On Wed, Dec 05, 2018 at 08:28:05PM +0900, Masahiro Yamada wrote:
> Some time ago, Sam pointed out a certain degree of overwrap between
> generic-y and mandatory-y. (https://lkml.org/lkml/2017/7/10/121)
>
> I a bit tweaked the meaning of mandatory-y; now it defines the minimum
> set of ASM headers that all architectures must have.
>
> If arch does not have specific implementation of a mandatory header,
> Kbuild will let it fallback to the asm-generic one by automatically
> generating a wrapper. This will allow to drop lots of redundant
> generic-y defines.
>
> Previously, "mandatory" was used in the context of UAPI, but I guess
> this can be extended to kernel space ASM headers.
>
> Suggested-by: Sam Ravnborg <sam@ravnborg.org>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Nice work!
For the full series:
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Have you considered to warn if generic-y contains a header listed
in mandatory-y - to prevent that they sneak back in.
And to catch when we lift a header from available to mandatory.
Sam
next prev parent reply other threads:[~2018-12-06 18:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 11:28 [PATCH 1/3] kbuild: refactor Makefile.asm-generic Masahiro Yamada
2018-12-05 11:28 ` [PATCH 2/3] kbuild: generate asm-generic wrappers if mandatory headers are missing Masahiro Yamada
2018-12-06 15:03 ` Christoph Hellwig
2018-12-11 12:59 ` Masahiro Yamada
2018-12-11 16:29 ` Palmer Dabbelt
2018-12-06 18:04 ` Sam Ravnborg [this message]
2018-12-11 13:01 ` Masahiro Yamada
2018-12-05 11:28 ` [PATCH 3/3] arch: remove redundant generic-y defines Masahiro Yamada
2018-12-05 11:28 ` Masahiro Yamada
2018-12-05 11:28 ` [OpenRISC] " Masahiro Yamada
2018-12-05 11:28 ` Masahiro Yamada
2018-12-05 11:28 ` Masahiro Yamada
2018-12-05 14:44 ` Christoph Hellwig
2018-12-05 14:44 ` Christoph Hellwig
2018-12-05 14:44 ` [OpenRISC] " Christoph Hellwig
2018-12-05 14:44 ` Christoph Hellwig
2018-12-05 14:44 ` Christoph Hellwig
2018-12-05 14:45 ` Christoph Hellwig
2018-12-05 14:45 ` Christoph Hellwig
2018-12-05 14:45 ` [OpenRISC] " Christoph Hellwig
2018-12-05 14:45 ` Christoph Hellwig
2018-12-05 14:45 ` Christoph Hellwig
2018-12-16 15:24 ` [PATCH 1/3] kbuild: refactor Makefile.asm-generic 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=20181206180459.GA19166@ravnborg.org \
--to=sam@ravnborg.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.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.