From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Adrian Bunk <bunk@stusta.de>
Cc: Ben Dooks <ben-linux@fluff.org>, linux-kernel@vger.kernel.org
Subject: Re: fs/fat - fix sparse warning
Date: Thu, 03 Nov 2005 03:39:32 +0900 [thread overview]
Message-ID: <87br12c2sb.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20051102180401.GA4272@stusta.de> (Adrian Bunk's message of "Wed, 2 Nov 2005 19:04:01 +0100")
Adrian Bunk <bunk@stusta.de> writes:
> It sometimes happens that the signature of a function changes and it is
> forgotten to update all prototypes.
>
> If the prototype is in a header file, gcc tells about the mistake.
>
> If the prototype is in the C file gcc can't help us and it might take
> some time until someone tracks the source of the nasty runtime problems
> this might cause.
>
> It's your choice as subsystem maintainer which header file the
> prototypes should go into - it is only important that both the file with
> the actual function and all users of this function #include this header.
Sounds reasonable, although that's unlikely, because those are
init/exit functions. OK, I'll do this in header cleanup as soon as possible.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2005-11-02 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 11:36 fs/fat - fix sparse warning Ben Dooks
2005-10-31 13:27 ` Alexey Dobriyan
2005-10-31 14:15 ` OGAWA Hirofumi
2005-11-02 18:04 ` Adrian Bunk
2005-11-02 18:39 ` OGAWA Hirofumi [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=87br12c2sb.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=ben-linux@fluff.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox