linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Olof's autobuilder <build@lixom.net>,
	olof@lixom.net, khilman@linaro.org,
	kernel-build-reports@lists.linaro.org,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: arm-soc build: 12 warnings 0 failures (arm-soc/v3.15-rc6-907-ge7c189d)
Date: Fri, 23 May 2014 17:25:29 -0700	[thread overview]
Message-ID: <537FE6F9.6060405@codeaurora.org> (raw)
In-Reply-To: <537fd99a.27da420a.0fb1.015c@mx.google.com>

On 05/23/14 16:28, Olof's autobuilder wrote:
> Warnings:
>       1 arch/arm/mach-msm/board-trout-gpio.c:120:2: warning: passing argument 2 of '__raw_writeb' makes pointer from integer without a cast [enabled by default]
>       1 arch/arm/mach-msm/board-trout-gpio.c:135:2: warning: passing argument 2 of '__raw_writeb' makes pointer from integer without a cast [enabled by default]
>       1 arch/arm/mach-msm/board-trout-gpio.c:151:2: warning: passing argument 2 of '__raw_writeb' makes pointer from integer without a cast [enabled by default]
>       1 arch/arm/mach-msm/board-trout-gpio.c:181:3: warning: passing argument 1 of '__raw_readb' makes pointer from integer without a cast [enabled by default]
>       1 arch/arm/mach-msm/board-trout-gpio.c:184:4: warning: passing argument 2 of '__raw_writeb' makes pointer from integer without a cast [enabled by default]

These are fixed[1] but it hasn't been picked up and sent to arm-soc.

[1] https://lkml.org/lkml/2014/2/26/733

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

           reply	other threads:[~2014-05-24  0:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <537fd99a.27da420a.0fb1.015c@mx.google.com>]

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=537FE6F9.6060405@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=build@lixom.net \
    --cc=galak@codeaurora.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=khilman@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).