From: Sam Ravnborg <sam@ravnborg.org>
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [Patch] kbuild: fix a compile warning
Date: Sat, 6 Jun 2009 00:08:42 +0200 [thread overview]
Message-ID: <20090605220842.GI29008@uranus.ravnborg.org> (raw)
In-Reply-To: <20090515075229.11346.6710.sendpatchset@localhost.localdomain>
On Fri, May 15, 2009 at 03:51:18AM -0400, Amerigo Wang wrote:
>
> I got this warning:
>
> HOSTCC scripts/basic/fixdep
> scripts/basic/fixdep.c: In function 'traps':
> scripts/basic/fixdep.c:377: warning: dereferencing type-punned pointer will break strict-aliasing rules
> scripts/basic/fixdep.c:379: warning: dereferencing type-punned pointer will break strict-aliasing rules
>
> Patch below fixes it.
We do not use -fno-strict-aliasing at userspace, so fix seems ok.
Applied.
Sam
prev parent reply other threads:[~2009-06-05 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 7:51 [Patch] kbuild: fix a compile warning Amerigo Wang
2009-05-28 7:41 ` Andrew Morton
2009-05-31 2:25 ` Amerigo Wang
2009-09-13 14:05 ` Felipe Contreras
2009-09-15 8:04 ` Amerigo Wang
2009-09-15 8:33 ` Felipe Contreras
2009-05-28 13:18 ` Luming Yu
2009-06-05 22:08 ` Sam Ravnborg [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=20090605220842.GI29008@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=linux-kernel@vger.kernel.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