From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] ia64 aliasing-test: fix gcc warnings on non-ia64
Date: Wed, 16 Jan 2008 11:05:19 -0700 [thread overview]
Message-ID: <200801161105.19820.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20080115160510.76d2bfbc.randy.dunlap@oracle.com>
On Tuesday 15 January 2008 05:05:10 pm Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Eliminate all build warnings. OK, these build warnings are from
> a build on x86_64. When I build on ia64, I don't see warnings.
> ...
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Acked-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Thanks, Randy.
> ---
> Documentation/ia64/aliasing-test.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> --- linux-2.6.24-rc7.orig/Documentation/ia64/aliasing-test.c
> +++ linux-2.6.24-rc7/Documentation/ia64/aliasing-test.c
> @@ -16,6 +16,7 @@
> #include <fcntl.h>
> #include <fnmatch.h>
> #include <string.h>
> +#include <sys/ioctl.h>
> #include <sys/mman.h>
> #include <sys/stat.h>
> #include <unistd.h>
> @@ -65,7 +66,7 @@ int scan_tree(char *path, char *file, of
> {
> struct dirent **namelist;
> char *name, *path2;
> - int i, n, r, rc, result = 0;
> + int i, n, r, rc = 0, result = 0;
> struct stat buf;
>
> n = scandir(path, &namelist, 0, alphasort);
> @@ -113,7 +114,7 @@ skip:
> free(namelist[i]);
> }
> free(namelist);
> - return rc;
> + return result;
> }
>
> char buf[1024];
> @@ -149,7 +150,7 @@ int scan_rom(char *path, char *file)
> {
> struct dirent **namelist;
> char *name, *path2;
> - int i, n, r, rc, result = 0;
> + int i, n, r, rc = 0, result = 0;
> struct stat buf;
>
> n = scandir(path, &namelist, 0, alphasort);
> @@ -180,7 +181,7 @@ int scan_rom(char *path, char *file)
> * important thing is that no MCA happened.
> */
> if (rc > 0)
> - fprintf(stderr, "PASS: %s read %ld bytes\n", path2, rc);
> + fprintf(stderr, "PASS: %s read %d bytes\n", path2, rc);
> else {
> fprintf(stderr, "PASS: %s not readable\n", path2);
> return rc;
> @@ -201,10 +202,10 @@ skip:
> free(namelist[i]);
> }
> free(namelist);
> - return rc;
> + return result;
> }
>
> -int main()
> +int main(void)
> {
> int rc;
>
> @@ -256,4 +257,6 @@ int main()
> scan_tree("/proc/bus/pci", "??.?", 0xA0000, 0x20000, 0);
> scan_tree("/proc/bus/pci", "??.?", 0xC0000, 0x40000, 1);
> scan_tree("/proc/bus/pci", "??.?", 0, 1024*1024, 0);
> +
> + return rc;
> }
>
prev parent reply other threads:[~2008-01-16 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 0:05 Randy Dunlap
2008-01-16 18:05 ` Bjorn Helgaas [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=200801161105.19820.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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
all inboxes | Powered by JetHome®