public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Vincent Stehlé" <vincent.stehle@freescale•com>
To: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	linux-arm-kernel@lists•infradead.org
Cc: "Vincent Stehlé" <vincent.stehle@freescale•com>,
	"Robin Holt" <holt@sgi•com>,
	"Michal Simek" <michal.simek@xilinx•com>,
	"Russell King" <linux@arm•linux.org.uk>,
	trivial@kernel•org
Subject: [PATCH linux-next] arm: zynq: fix compilation warning
Date: Thu, 27 Jun 2013 14:42:41 +0200	[thread overview]
Message-ID: <1372336962-6459-1-git-send-email-vincent.stehle@freescale.com> (raw)

Fix the following compilation warning:

  arch/arm/mach-zynq/common.c:110:2: warning: initialization from incompatible pointer type [enabled by default]
  arch/arm/mach-zynq/common.c:110:2: warning: (near initialization for ‘__mach_desc_XILINX_EP107.restart’) [enabled by default]

Signed-off-by: Vincent Stehlé <vincent.stehle@freescale•com>
Cc: Robin Holt <holt@sgi•com>
Cc: Michal Simek <michal.simek@xilinx•com>
Cc: Russell King <linux@arm•linux.org.uk>
Cc: trivial@kernel•org
---


Hi,

This warning was seen on linux-next tag next-20130627, with config ARM
multi_v7_defconfig.

Best regards,

V.


 arch/arm/mach-zynq/common.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/mach-zynq/common.c b/arch/arm/mach-zynq/common.c
index 4130e65..8ea5f11 100644
--- a/arch/arm/mach-zynq/common.c
+++ b/arch/arm/mach-zynq/common.c
@@ -91,7 +91,7 @@ static void __init zynq_map_io(void)
 	zynq_scu_map_io();
 }
 
-static void zynq_system_reset(char mode, const char *cmd)
+static void zynq_system_reset(enum reboot_mode mode, const char *cmd)
 {
 	zynq_slcr_system_reset();
 }
-- 
1.7.10.4

             reply	other threads:[~2013-06-27 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 12:42 Vincent Stehlé [this message]
2013-06-27 13:01 ` [PATCH linux-next] arm: zynq: fix compilation warning Michal Simek
2013-06-28  0:38   ` Stephen Rothwell
2013-07-23 18:03     ` Olof Johansson

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=1372336962-6459-1-git-send-email-vincent.stehle@freescale.com \
    --to=vincent.stehle@freescale$(echo .)com \
    --cc=holt@sgi$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux@arm$(echo .)linux.org.uk \
    --cc=michal.simek@xilinx$(echo .)com \
    --cc=trivial@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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