All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Hirokazu Takata <takata@linux-m32r.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	"dhowells@redhat.com" <dhowells@redhat.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-m32r@ml.linux-m32r.org, linux-m32r-ja@ml.linux-m32r.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux-Arch <linux-arch@vger.kernel.org>
Subject: [PATCH] arch: m32r: kernel: use 'COPY_UNALIGNED_HWORD' instead of 'COPY_UNALIGNED_WORD'
Date: Wed, 26 Jun 2013 11:58:53 +0800	[thread overview]
Message-ID: <51CA66FD.1010708@asianux.com> (raw)

For 'hvalue' and 'hlocation', need use 'COPY_UNALIGNED_HWORD' instead

The related warnings (with allmodconfig)
    CC      arch/m32r/kernel/module.o
  arch/m32r/kernel/module.c: In function ‘apply_relocate_add’:
  arch/m32r/kernel/module.c:127:8: warning: ‘*((void *)&hvalue+2)’ is used uninitialized in this function [-Wuninitialized]
  arch/m32r/kernel/module.c:127:8: warning: ‘*((void *)&hvalue+2)’ is used uninitialized in this function [-Wuninitialized]
  arch/m32r/kernel/module.c:127:8: warning: ‘*((void *)&hvalue+3)’ is used uninitialized in this function [-Wuninitialized]

Signed-off-by: Chen Gang <gang.chen@asianux.com>
---
 arch/m32r/kernel/module.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/m32r/kernel/module.c b/arch/m32r/kernel/module.c
index 38233b6..bcad14c 100644
--- a/arch/m32r/kernel/module.c
+++ b/arch/m32r/kernel/module.c
@@ -124,7 +124,7 @@ int apply_relocate_add(Elf32_Shdr *sechdrs,
                         relocation = relocation & 0xffff;
 			/* RELA must has 0 at relocation field. */
 			hvalue = relocation;
-	    		COPY_UNALIGNED_WORD (hvalue, *hlocation, align);
+			COPY_UNALIGNED_HWORD(hvalue, *hlocation, align);
 			break;
 		case R_M32R_SDA16_RELA:
 		case R_M32R_LO16_RELA:
-- 
1.7.7.6

                 reply	other threads:[~2013-06-26  3:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51CA66FD.1010708@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=dhowells@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m32r-ja@ml.linux-m32r.org \
    --cc=linux-m32r@ml.linux-m32r.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sam@ravnborg.org \
    --cc=takata@linux-m32r.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.