From: Richard Weinberger <richard@nod.at>
To: masahiroy <masahiroy@kernel.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: disable header exports for UML in a straightforward way
Date: Thu, 1 Sep 2022 08:00:55 +0200 (CEST) [thread overview]
Message-ID: <318503440.165958.1662012055078.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20220901011252.550830-1-masahiroy@kernel.org>
----- Ursprüngliche Mail -----
> Von: "masahiroy" <masahiroy@kernel.org>
> An: "linux-kbuild" <linux-kbuild@vger.kernel.org>
> CC: "masahiroy" <masahiroy@kernel.org>, "Michal Marek" <michal.lkml@markovi.net>, "Nick Desaulniers"
> <ndesaulniers@google.com>, "Randy Dunlap" <rdunlap@infradead.org>, "richard" <richard@nod.at>, "linux-kernel"
> <linux-kernel@vger.kernel.org>
> Gesendet: Donnerstag, 1. September 2022 03:12:52
> Betreff: [PATCH] kbuild: disable header exports for UML in a straightforward way
> Previously 'make ARCH=um headers' stopped because of missing
> arch/um/include/uapi/asm/Kbuild.
>
> The error is not shown since commit ed102bf2afed ("um: Fix W=1
> missing-include-dirs warnings") because UML got
> arch/um/include/uapi/asm/Kbuild.
>
> Hard-code the unsupported architecture, so it works like before.
>
> Fixes: ed102bf2afed ("um: Fix W=1 missing-include-dirs warnings")
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
prev parent reply other threads:[~2022-09-01 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 1:12 [PATCH] kbuild: disable header exports for UML in a straightforward way Masahiro Yamada
2022-09-01 6:00 ` Richard Weinberger [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=318503440.165958.1662012055078.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=rdunlap@infradead.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