From: Mark Brown <broonie@kernel.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: alsa-devel@alsa-project.org, richard.genoud@gmail.com,
linux-sound@vger.kernel.org, Bo Shen <voice.shen@atmel.com>,
plagnioj@jcrosoft.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [Patch v2 2/2] ASoC: atmel: sam9x5_wm8731: remove platform_set_drvdata
Date: Mon, 09 Dec 2013 16:58:53 +0000 [thread overview]
Message-ID: <20131209165853.GS29268@sirena.org.uk> (raw)
In-Reply-To: <52A59955.8000100@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Mon, Dec 09, 2013 at 11:20:05AM +0100, Nicolas Ferre wrote:
> It seems that this patch has not been applied to your "next" branch
> (aka ping)...
If you think something has been forgotten please resend. If it's
genuinely been lost it's going to need resending and the mail just leads
to more mails, a resend can be directly applied. I had thought I'd
replied to this at the time but it seems I didn't, or at least I can't
see my reply on the list... sorry about that.
The question was if we should change this or if we should change the
core to not overwrite something that probably ought to be the driver's
domain? Looking at the code I think we're probably doing the right
thing but it'd be good to consider.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-09 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 10:05 [Patch v2 1/2] ASoC: atmel: sam9x5_wm8731: fix oops when unload module Bo Shen
2013-11-27 10:05 ` [Patch v2 2/2] ASoC: atmel: sam9x5_wm8731: remove platform_set_drvdata Bo Shen
2013-12-09 10:20 ` Nicolas Ferre
2013-12-09 16:58 ` Mark Brown [this message]
2013-12-18 6:55 ` [RESEND PATCH " Bo Shen
2013-12-31 12:27 ` [Patch " Mark Brown
2013-11-27 15:50 ` [Patch v2 1/2] ASoC: atmel: sam9x5_wm8731: fix oops when unload module Mark Brown
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=20131209165853.GS29268@sirena.org.uk \
--to=broonie@kernel.org \
--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=richard.genoud@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox