mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	linux-mips@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: Remove posix_types.h include from sigcontext.h
Date: Wed, 04 Sep 2024 18:02:49 +0800	[thread overview]
Message-ID: <f47376d9dfc174fc6eeb29ee45c67413ecc1feb6.camel@xry111.site> (raw)
In-Reply-To: <alpine.DEB.2.21.2409040229030.1802@angie.orcam.me.uk>

On Wed, 2024-09-04 at 03:06 +0100, Maciej W. Rozycki wrote:
> -#include <linux/types.h>
> -
>  /*
>   * Keep this struct definition in sync with the sigcontext fragment
>   * in arch/mips/tools/offset.c
> @@ -66,6 +64,9 @@ struct sigcontext {
>  };
>  
>  #ifdef __KERNEL__
> +
> +#include <linux/posix_types.h>
> +
>  struct sigcontext32 {
>  	__u32	sc_regmask;		/* Unused */
>  	__u32	sc_status;
> 
> so not without explanation and clearly to address a userland compilation 
> issue.  It seems that the original directive should have just been moved 
> into the __KERNEL__ part without changing the file included though.

Yes, I just mean *changing* the include file is not explained and it
seems an error.  I'm not familiar with ancient kernels but AFAIK for
using __u32 etc. we should use linux/types.h since Linux 1.2.

Moving the include into #ifdef __KERNEL__ makes sense to me.

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2024-09-04 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28  3:04 Xi Ruoyao
2024-08-29  8:49 ` Thomas Bogendoerfer
2024-09-04  2:06 ` Maciej W. Rozycki
2024-09-04 10:02   ` Xi Ruoyao [this message]
2024-09-04 12:49     ` Maciej W. Rozycki

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=f47376d9dfc174fc6eeb29ee45c67413ecc1feb6.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=tsbogend@alpha.franken.de \
    /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®