mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Olaf Hering <olaf@aepfle.de>, Lv Zheng <lv.zheng@intel.com>
Cc: Robert Moore <robert.moore@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, devel@acpica.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPICA: remove duplicate u8 typedef
Date: Wed, 29 Apr 2015 02:43:31 +0200	[thread overview]
Message-ID: <1624281.lNzTEna4Ru@vostro.rjw.lan> (raw)
In-Reply-To: <1430232844-11018-1-git-send-email-olaf@aepfle.de>

On Tuesday, April 28, 2015 04:54:04 PM Olaf Hering wrote:
> During commit e252652fb2664d42de19f933aa3688bbc470de3f ("ACPICA:
> acpidump: Remove integer types translation protection.") two 'unsigned
> char' types got converted to 'u8'.
> 
> The result does not compile with gcc-4.5, it can not cope with duplicate
> typedefs.
> 
> Signed-off-by: Olaf Hering <olaf@aepfle.de>

Applied, thanks!

Lv, can you please see if that's an upstream issue too?

> ---
>  include/acpi/actypes.h | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/include/acpi/actypes.h b/include/acpi/actypes.h
> index f5ca0e9..1c3002e 100644
> --- a/include/acpi/actypes.h
> +++ b/include/acpi/actypes.h
> @@ -124,7 +124,6 @@
>  #ifndef ACPI_USE_SYSTEM_INTTYPES
>  
>  typedef unsigned char u8;
> -typedef unsigned char u8;
>  typedef unsigned short u16;
>  typedef short s16;
>  typedef COMPILER_DEPENDENT_UINT64 u64;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  parent reply	other threads:[~2015-04-29  0:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 14:54 Olaf Hering
2015-04-29  0:27 ` Zheng, Lv
2015-04-29  0:43 ` Rafael J. Wysocki [this message]
2015-04-29  0:29   ` Zheng, Lv

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=1624281.lNzTEna4Ru@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=devel@acpica.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=olaf@aepfle.de \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@intel.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®