From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-sound@vger.kernel.org, alsa-devel@alsa-project.org,
nicolas.ferre@atmel.com, plagnioj@jcrosoft.com
Subject: Re: [PATCH 1/2] ASoC: atmel-ssc: use devm_xxx() managed function
Date: Tue, 16 Oct 2012 14:12:24 +0900 [thread overview]
Message-ID: <20121016051221.GA8670@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1350359819-2461-1-git-send-email-voice.shen@atmel.com>
On Tue, Oct 16, 2012 at 11:56:58AM +0800, Bo Shen wrote:
> Using the devm_xxx() managed function to stripdown the error
> and remove code.
Applied both, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-sound@vger.kernel.org, alsa-devel@alsa-project.org,
nicolas.ferre@atmel.com, plagnioj@jcrosoft.com
Subject: Re: [PATCH 1/2] ASoC: atmel-ssc: use devm_xxx() managed function
Date: Tue, 16 Oct 2012 05:12:24 +0000 [thread overview]
Message-ID: <20121016051221.GA8670@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1350359819-2461-1-git-send-email-voice.shen@atmel.com>
On Tue, Oct 16, 2012 at 11:56:58AM +0800, Bo Shen wrote:
> Using the devm_xxx() managed function to stripdown the error
> and remove code.
Applied both, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ASoC: atmel-ssc: use devm_xxx() managed function
Date: Tue, 16 Oct 2012 14:12:24 +0900 [thread overview]
Message-ID: <20121016051221.GA8670@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1350359819-2461-1-git-send-email-voice.shen@atmel.com>
On Tue, Oct 16, 2012 at 11:56:58AM +0800, Bo Shen wrote:
> Using the devm_xxx() managed function to stripdown the error
> and remove code.
Applied both, thanks.
next prev parent reply other threads:[~2012-10-16 5:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 3:56 [PATCH 1/2] ASoC: atmel-ssc: use devm_xxx() managed function Bo Shen
2012-10-16 3:56 ` Bo Shen
2012-10-16 3:56 ` Bo Shen
2012-10-16 3:56 ` [PATCH 2/2] ASoC: atmel-ssc: use module_platform_driver macro Bo Shen
2012-10-16 3:56 ` Bo Shen
2012-10-16 3:56 ` Bo Shen
2012-10-16 8:07 ` Nicolas Ferre
2012-10-16 8:07 ` Nicolas Ferre
2012-10-16 8:07 ` Nicolas Ferre
2012-10-16 8:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-16 8:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-16 8:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-16 8:59 ` Bo Shen
2012-10-16 8:59 ` Bo Shen
2012-10-16 8:59 ` Bo Shen
2012-10-16 9:07 ` Russell King - ARM Linux
2012-10-16 9:07 ` Russell King - ARM Linux
2012-10-16 9:07 ` Russell King - ARM Linux
2012-10-16 9:32 ` Fabio Porcedda
2012-10-16 9:32 ` Fabio Porcedda
2012-10-16 9:32 ` Fabio Porcedda
2012-10-16 5:12 ` Mark Brown [this message]
2012-10-16 5:12 ` [PATCH 1/2] ASoC: atmel-ssc: use devm_xxx() managed function Mark Brown
2012-10-16 5:12 ` Mark Brown
2012-10-16 8:05 ` Nicolas Ferre
2012-10-16 8:05 ` Nicolas Ferre
2012-10-16 8:05 ` Nicolas Ferre
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=20121016051221.GA8670@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=voice.shen@atmel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.