linux-kernel - Re: [PATCH] Documentation/firmware_class/firmware_sample

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a781481a0706280335l5ac5e0e1w6c29922598b7416f@mail.gmail.com>
Date:	Thu, 28 Jun 2007 16:05:48 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
To:	"Anders Blomdell" <anders.blomdell@...trol.lth.se>
Cc:	linux-kernel@...r.kernel.org,
	"Manuel Estrada Sainz" <ranty@...ian.org>
Subject: Re: [PATCH] Documentation/firmware_class/firmware_sample_driver.c

Hi,

[ It's good that you're trying to fix this, code in documentation should
be setting standards, clearly. ]

On 6/27/07, Anders Blomdell <anders.blomdell@...trol.lth.se> wrote:
> [...]
> Minor modifications to make the example load and unload without Oops
> [...]
>  static int sample_init(void)
>  {
> -       device_initialize(&ghost_device);
> +       device_register(&ghost_device);
>         /* since there is no real hardware insertion I just call the
>          * sample probe functions here */
> -       sample_probe_specific();
> +       /* sample_probe_specific(); */
>         sample_probe_default();
> -       sample_probe_async();
> +       /*sample_probe_async();*/
>         return 0;
>  }

But IMO the above functions should be *fixed* to work properly instead
of simply commenting them out. If they are un-fixable, why even keep
the broken code in that file (only to mislead readers in future?). You
might as well remove those calls (and the function definitions) completely.
Best would be to fix them, of course.

My Rs. 0.02,
Satyam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/