From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 0/4] ARM: Basic Xilinx Support
Date: Mon, 28 Feb 2011 11:19:49 +0000 [thread overview]
Message-ID: <20110228111949.GC2754@pulham.picochip.com> (raw)
In-Reply-To: <0d410c20-32b4-46d6-9639-249a2816cbe9@VA3EHSMHS005.ehs.local>
On Fri, Feb 18, 2011 at 11:14:37AM -0700, John Linn wrote:
>
> V4
>
> I incorporated more feedback from Jamie Iles. It was
> primariy cleanup with the only significant change
> being a move to using raw_read/write in the uncompressor
> uart code.
>
> The other changes were minor updates so that the patch
> set applies to linux-next.
>
> This patch set is now tested against the linux-next branch
> from pub/scm/linux/kernel/git/sfr/linux-next.git.
Hi John,
I've just tried a quick dummy build of this series (with a fudge in
mach-types to get it building) and I see a couple of minor sparse
warnings:
arch/arm/mach-xilinx/common.c:54:13: warning: symbol
'xilinx_system_init' was not declared. Should it be static?
arch/arm/mach-xilinx/common.c:68:13: warning: symbol 'xilinx_irq_init'
was not declared. Should it be static?
arch/arm/mach-xilinx/common.c:110:13: warning: symbol 'xilinx_map_io'
was not declared. Should it be static?
arch/arm/mach-xilinx/timer.c:290:18: warning: symbol 'xttcpss_sys_timer'
was not declared. Should it be static?
I think all of these can be resolved by including "common.h" in both
timer.c and common.c.
I've put a couple of nitpicks for the individual patches, sorry I didn't
spot them before. Otherwise,
Reviewed-by: Jamie Iles <jamie@jamieiles.com>
Jamie
next prev parent reply other threads:[~2011-02-28 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 18:14 [PATCH V4 0/4] ARM: Basic Xilinx Support John Linn
2011-02-28 11:19 ` Jamie Iles [this message]
2011-02-28 14:22 ` John Linn
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=20110228111949.GC2754@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).