From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/2] ARM: pxa: spitz: register spitz-audio device
Date: Wed, 22 Oct 2014 10:46:06 +0200 [thread overview]
Message-ID: <1935279.fumFSz5CfW@wuerfel> (raw)
In-Reply-To: <1413926133-3566-1-git-send-email-dbaryshkov@gmail.com>
On Wednesday 22 October 2014 01:15:32 Dmitry Eremin-Solenikov wrote:
> Register spitz-audio device to be used by ASoC driver.
>
> [V2: Removed ifdefs around spitz_audio_init].
>
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> ---
>
A more general note about your patch description above: when you
write about the changes between versions, put that below the ---
line under your Signed-off-by. Aside from that, your changelog
entry would actually benefit from more verbosity: explain what the
purpose of this is, not just what it does.
> /**************************************************************************
> ****>
> + * Audio devices
> +
> ***************************************************************************
> ***/ +static struct platform_device spitz_audio_device = {
> + .name = "spitz-audio",
> + .id = -1,
> +};
> +
> +static inline void spitz_audio_init(void)
> +{
> + platform_device_register(&spitz_audio_device);
> +}+
I realize that the file has more of these, but it would be better
for a number of reasons to use 'platform_device_register_simple'
instead of platform_device_register. statically defining platform
devices (or any other device) is not recommended.
Arnd
next prev parent reply other threads:[~2014-10-22 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 21:15 [PATCH V2 1/2] ARM: pxa: spitz: register spitz-audio device Dmitry Eremin-Solenikov
2014-10-21 21:15 ` [PATCH V2 2/2] ASoC: pxa: Convert spitz to use snd_soc_register_card() Dmitry Eremin-Solenikov
2014-10-22 8:46 ` Arnd Bergmann [this message]
2014-10-22 9:42 ` [PATCH V2 1/2] ARM: pxa: spitz: register spitz-audio device Dmitry Eremin-Solenikov
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=1935279.fumFSz5CfW@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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