From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, Nicolin Chen <b42378@freescale.com>,
Mark Brown <broonie@kernel.org>,
kernel@pengutronix.de, Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH v2 2/2] ASoC: fsl: add imx-ssm2603 machine driver
Date: Thu, 30 Jan 2014 17:49:57 +0800 [thread overview]
Message-ID: <20140130094956.GA5189@MrMyself> (raw)
In-Reply-To: <1391075058-3731-2-git-send-email-p.zabel@pengutronix.de>
On Thu, Jan 30, 2014 at 10:44:18AM +0100, Philipp Zabel wrote:
> +static int imx_ssm2603_remove(struct platform_device *pdev)
> +{
> + return 0;
> +}
I think we can drop this remove() here right :)
Best regards,
Nicolin
prev parent reply other threads:[~2014-01-30 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 9:44 [PATCH v2 1/2] ASoC: imx-audmux: add RXFS/RXCLK defines for 6-wire connections Philipp Zabel
2014-01-30 9:44 ` [PATCH v2 2/2] ASoC: fsl: add imx-ssm2603 machine driver Philipp Zabel
2014-01-30 9:49 ` Nicolin Chen [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=20140130094956.GA5189@MrMyself \
--to=guangyu.chen@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=kernel@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=shawn.guo@linaro.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