From: ht-lab <hans64@ht-lab.com>
To: Juan Perez-Sanchez <lithoxs@gmail.com>
Cc: linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: [PATCH] Ansi-C compatibility fixes
Date: Sun, 22 Jul 2012 09:45:14 +0100 [thread overview]
Message-ID: <500BBD9A.8020407@ht-lab.com> (raw)
In-Reply-To: <CAD6VGuYwx=TSrX_prceFagsZZEPqw4EyraNf+iYND+8K_=6YUw@mail.gmail.com>
Hi Juan,
You seem to be doing a lot of good work, I would be interested to hear
what it is that you are working on,
Regards,
Hans
www.ht-lab.com
On 19/07/2012 23:37, Juan Perez-Sanchez wrote:
> Hi,
>
>
> This patch makes another round of fixes to improve ansi-C
> compatibility, this time using the open-watcom compiler. An effort was
> done to make the right changes to code, not just wipe out the errors
> or warnings. For example, if prototypes, definition and usage of
> functions differ, examined the purpose and uses of the function to
> determine the right fix.
>
> The partial list of fixes includes:
>
> - Missing prototypes of functions.
> - Assignment of variables without appropriate casting.
> - Inadequate typing of variables.
> - Differences in definition, prototypes and use.
> - Functions defined to return some value but did not return anything.
> - Definition of zero length arrays.
>
> Code size is unchanged.
>
> The Image builded without errors. The kernel was tested with QEMU and
> dioscuri emulators. Also in a PPro pc booting from floppy.
>
> Greetings,
>
> Juan
next prev parent reply other threads:[~2012-07-22 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 22:37 [PATCH] Ansi-C compatibility fixes Juan Perez-Sanchez
2012-07-22 8:45 ` ht-lab [this message]
2012-08-11 15:22 ` Jody Bruchon
2012-08-20 19:30 ` Bojan Popovic
2012-11-12 23:17 ` Juan Perez-Sanchez
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=500BBD9A.8020407@ht-lab.com \
--to=hans64@ht-lab.com \
--cc=linux-8086@vger.kernel.org \
--cc=lithoxs@gmail.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