From: Thomas Gleixner <tglx@linutronix.de>
To: Vadim Pasternak <vadimp@mellanox.com>
Cc: mingo@redhat.com, hpa@zytor.com, davem@davemloft.net,
geert@linux-m68k.org, akpm@linux-foundation.org,
gregkh@linuxfoundation.org, kvalo@codeaurora.org,
mchehab@kernel.org, linux@roeck-us.net, x86@kernel.org,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, jiri@resnulli.us
Subject: Re: [patch v5] x86/platform/mellanox: introduce support for Mellanox systems platform
Date: Thu, 22 Sep 2016 19:08:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1609221902570.5599@nanos> (raw)
In-Reply-To: <1474365532-168129-1-git-send-email-vadimp@mellanox.com>
On Tue, 20 Sep 2016, vadimp@mellanox.com wrote:
Just a few nitpicks.
> +/* Regions for LPC I2C controller and LPC base register space */
> +static struct resource mlxplat_lpc_resources[] = {
Shouldnt this be const?
> +static int mlxplat_default_channels[][8] = {
> + {
Ditto. And some more of these?
> +static struct dmi_system_id mlxplat_dmi_table[] __initdata = {
This one as well.
> +static int __init mlxplat_init(void)
> +{
> + struct mlxplat_priv *priv;
> + int i;
> + int err;
Same types can go into one line.
> +
> + return err;
err is unitialized if we get here. Just return 0 and be done with it.
> +
> +fail_platform_mux_register:
> +static void __exit mlxplat_exit(void)
> +{
> + struct mlxplat_priv *priv = platform_get_drvdata(mlxplat_dev);
> + int i;
> +
> + for (i = ARRAY_SIZE(mlxplat_mux_data) - 1; i >= 0 ; i--)
> + platform_device_unregister(priv->pdev_mux[i]);
> +
> + platform_device_unregister(priv->pdev_i2c);
> + platform_device_unregister(mlxplat_dev);
> +}
> +
> +module_init(mlxplat_init);
> +module_exit(mlxplat_exit);
Please move the module_xxx() right under the closing brace of the function
to which it belongs.
Otherwise this looks good.
Thanks,
tglx
prev parent reply other threads:[~2016-09-22 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 9:58 vadimp
2016-09-22 17:08 ` Thomas Gleixner [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=alpine.DEB.2.20.1609221902570.5599@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jiri@resnulli.us \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab@kernel.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@mellanox.com \
--cc=x86@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
all inboxes | Powered by JetHome®