From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] arch/i386/kernel/acpi/boot.c
Date: Sun, 27 Feb 2005 16:04:40 +0000 [thread overview]
Message-ID: <4221EF98.6080803@bfs.de> (raw)
In-Reply-To: <7a4211f805022518082a5c12a4@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
hi Jonathan,
the complain of ggc4 is correct. defining char and returning unsigned
char is wrong. but i would exspect a void * here as a quick look at
boot.c says that the result is always casted to some other struct foo *.
I am not an expert on that can someone please comment it ?
I found also no references outside boot.c perhaps 'static' is usefull here ?
re,
walter
Jonathan Stafford wrote:
> I've never done any kernel work before, but the gcc 4 warning fixes
> seems like a fairly easy place to start. As there will ultimately be
> several hundred patches, is there are particular order to fix these?
> I've been tinkering with them simply in compiled order.
>
> Should I be sending/cc'ing these patches to somewhere besides KJML as
> I write them? I know that many of the various parts have their own
> mailings lists, but I don't begin to know what all of them are. What
> about trivial patch monkey?
>
> Thanks,
> jonathan
>
> Here's my first would-be patch; anything I should change?
> ==============================================
>
> Description: Fixes gcc 4 warnings. See
> http://marc.theaimsgroup.com/?t=110348353800003 for details
>
> Signed-off-by: Jonathan Stafford <thecabinet@gmail.com>
>
> diff -Nru a/arch/i386/kernel/acpi/boot.c b/arch/i386/kernel/acpi/boot.c
> --- a/arch/i386/kernel/acpi/boot.c 2005-02-24 04:36:13 -05:00
> +++ b/arch/i386/kernel/acpi/boot.c 2005-02-24 04:36:13 -05:00
> @@ -153,7 +153,7 @@
> mapped_size += PAGE_SIZE;
> }
>
> - return ((unsigned char *) base + offset);
> + return ((char *) base + offset);
> }
> #endif
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kernel-janitors mailing list
> Kernel-janitors@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/kernel-janitors
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-02-27 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 2:08 [KJ] [PATCH] arch/i386/kernel/acpi/boot.c Jonathan Stafford
2005-02-26 5:43 ` Nish Aravamudan
2005-02-27 16:04 ` walter harms [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=4221EF98.6080803@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@vger.kernel.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.