From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alexander Lobakin <alobakin@pm.me>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
Paul Burton <paulburton@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH mips-next] MIPS: UAPI: unexport unistd_nr_{n32,n64,o32}.h
Date: Thu, 7 Jan 2021 17:25:49 +0100 [thread overview]
Message-ID: <20210107162549.GA11882@alpha.franken.de> (raw)
In-Reply-To: <20210104154115.213029-1-alobakin@pm.me>
On Mon, Jan 04, 2021 at 03:41:48PM +0000, Alexander Lobakin wrote:
> unistd_nr_{n32,n64,o32}.h are needed only by include/asm/unistd.h,
> which is a kernel-side header file, and their contents is generally
> not for userland use.
> Move their target destination from include/generated/uapi/asm/ to
> include/generated/asm/ to disable exporting them as UAPI headers.
>
> Signed-off-by: Alexander Lobakin <alobakin@pm.me>
> ---
> arch/mips/include/asm/Kbuild | 4 ++++
> arch/mips/include/uapi/asm/Kbuild | 3 ---
> arch/mips/kernel/syscalls/Makefile | 16 ++++++++--------
> 3 files changed, 12 insertions(+), 11 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-01-07 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 15:41 Alexander Lobakin
2021-01-07 16:25 ` Thomas Bogendoerfer [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=20210107162549.GA11882@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=akpm@linux-foundation.org \
--cc=alobakin@pm.me \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=paulburton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 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®