linux-kernel - Re: [PATCH 2/3] MFD: AB8500 debugfs

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]

Date:	Mon, 13 Sep 2010 15:26:19 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Mattias Wallin <mattias.wallin@...ricsson.com>
Cc:	linux-kernel@...r.kernel.org, broonie@...nsource.wolfsonmicro.com,
	elinwal <linus.walleij@...ricsson.com>
Subject: Re: [PATCH 2/3] MFD: AB8500 debugfs

Hi Mattias,

I have some addtional comments:

On Mon, Sep 13, 2010 at 10:33:02AM +0200, Mattias Wallin wrote:
> +static struct platform_driver ab8500_debug_driver = {
> +       .driver = {
> +               .name = "ab8500-debug",
> +               .owner = THIS_MODULE,
> +       },
> +       .probe  = ab8500_debug_probe,
> +       .remove = __devexit_p(ab8500_debug_remove)
> +};
> +
> +static int __init ab8500_debug_init(void)
> +{
> +       return platform_driver_register(&ab8500_debug_driver);
> +}
> +
> +static void __exit ab8500_debug_exit(void)
> +{
> +       platform_driver_unregister(&ab8500_debug_driver);
> +}
It seems a bit awkward to me to have this code as an actual platform driver.
Why not defining ab8500_debug_[probe|remove] in ab8500.h as no-op when
CONFIG_AB8500_DEBUG is not defined and as extern otherwise ?

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/