From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] LoongArch: Remove posix_types.h include from sigcontext.h
Date: Wed, 28 Aug 2024 12:27:20 +0800 [thread overview]
Message-ID: <e8cc0f2d1e82097ab8646edfdd2a4a1fca386bcc.camel@xry111.site> (raw)
In-Reply-To: <CAAhV-H5dDkyd5qkipwbKJvNduWM0UgENBqMHJGXhEoekizneaw@mail.gmail.com>
On Wed, 2024-08-28 at 12:11 +0800, Huacai Chen wrote:
> Hi, Ruoyao,
>
> Just some questions:
> 1, Changing UAPI is not a good idea.
But removing unneeded includes from UAPI is fine. For example, the
commit 44e0b165b6c078b84767da4ba06ffa27af562c96 has removed
linux/posix_types.h from termbits.h for all ports.
> 2. In another thread you said that "paper over" is not enough for some
> cases.
> 3. include/uapi/linux/types.h still include linux/posix_types.h, why
> your "paper over" works?
Well maybe it does not work (I've not seriously tested as it's just a
paper over). But removing unneeded include is correct on its own
anyway. And ...
> > The unneeded include was found debugging some vDSO self test build
> > failure (it's not the root cause though).
So it's just "found" debugging the issue. Maybe I should change "it's
not the root cause" to "it's not really related to that issue"?
>
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-08-28 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 3:14 Xi Ruoyao
2024-08-28 4:11 ` Huacai Chen
2024-08-28 4:27 ` Xi Ruoyao [this message]
2024-08-28 4:43 ` Huacai Chen
2024-08-29 7:30 ` Xi Ruoyao
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=e8cc0f2d1e82097ab8646edfdd2a4a1fca386bcc.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
/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®