linux-hexagon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rkuo <rkuo@codeaurora.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-hexagon@vger.kernel.org
Subject: Re: [PATCH] Revert "Hexagon: fix signal.c compile error"
Date: Thu, 23 Apr 2015 15:40:36 -0500	[thread overview]
Message-ID: <20150423204036.GA5404@codeaurora.org> (raw)
In-Reply-To: <1429752484-14499-1-git-send-email-vapier@gentoo.org>

On Wed, Apr 22, 2015 at 09:28:04PM -0400, Mike Frysinger wrote:
> This reverts commit f3f601c1d2728f02544cfd143eaa82e5398b3e9b.
> 
> UAPI headers cannot use "uapi/" in their paths by design -- when they're
> installed, they do not have the uapi/ prefix.  Otherwise doing so breaks
> userland badly.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
>  arch/hexagon/include/uapi/asm/signal.h | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/arch/hexagon/include/uapi/asm/signal.h b/arch/hexagon/include/uapi/asm/signal.h
> index 98106e5..24b9988 100644
> --- a/arch/hexagon/include/uapi/asm/signal.h
> +++ b/arch/hexagon/include/uapi/asm/signal.h
> @@ -19,8 +19,6 @@
>  #ifndef _ASM_SIGNAL_H
>  #define _ASM_SIGNAL_H
>  
> -#include <uapi/asm/registers.h>
> -
>  extern unsigned long __rt_sigtramp_template[2];
>  
>  void do_signal(struct pt_regs *regs);
> -- 
> 2.3.5
> 

I'll need to actually fix the thing the original commit was trying to fix,
but I can follow up with another patch.

Thanks!

Acked-by: Richard Kuo <rkuo@codeaurora.org>


-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, 
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-04-23 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23  1:28 [PATCH] Revert "Hexagon: fix signal.c compile error" Mike Frysinger
2015-04-23 20:40 ` rkuo [this message]
2015-04-24  3:59   ` Mike Frysinger

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=20150423204036.GA5404@codeaurora.org \
    --to=rkuo@codeaurora.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=vapier@gentoo.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;
as well as URLs for NNTP newsgroup(s).