On Tue, 18 Sep 2007 13:18:34 +0100 (BST)
"Maciej W. Rozycki" <email@example.com> wrote:
> Add error messages to the probe call.
> Signed-off-by: Maciej W. Rozycki <firstname.lastname@example.org>
> While they may rarely trigger, they may be useful when something weird is
> going on. Also this is good style.
> This is an updated version that addresses an issue raised by Mariusz
> Kozlowski for the sibling patch. Checked with checkpatch.pl.
> Please apply.
> diff -up --recursive --new-file
> --- linux-mips-2.6.23-rc5-20070904.macro/drivers/video/pmag-ba-fb.c
> 2007-02-21 05:56:47.000000000 +0000
> +++ linux-mips-2.6.23-rc5-20070904/drivers/video/pmag-ba-fb.c 2007-09-18
> 10:56:51.000000000 +0000
> @@ -147,16 +147,23 @@ static int __init pmagbafb_probe(struct
> resource_size_t start, len;
> struct fb_info *info;
> struct pmagbafb_par *par;
> + int err = 0;
This initialisation to zero is not good.
Because if some error-path code forgot to do `err = -EFOO' then probe()
will return zero and the driver will leave things in half-initialised state
and will then proceed as if things had succeeded. It will crash.
So it's better to leave this local uninitialised, because we really want to
get that compiler warning if someone forgot to set the return value.
I made that change, but am too stupid to be able to work out how to create
a config which will let me compile this thing.
akpm:/usr/src/25> grep PMAG arch/arm/configs/*