* Re: [PATCH] sound/soc-core: Don't overwrite .poweroff in snd_soc_pm_ops [not found] <a20a22fcfed7b4e62069ef8abebfa89f557646c2.1330080832.git.viresh.kumar@st.com> @ 2012-02-24 14:46 ` Mark Brown 2012-02-24 14:57 ` viresh kumar 0 siblings, 1 reply; 3+ messages in thread From: Mark Brown @ 2012-02-24 14:46 UTC (permalink / raw) To: Viresh Kumar Cc: pratyush.anand, alsa-devel, rajeev-dlh.kumar, bhavna.yadav, bhupesh.sharma, armando.visconti, mirko.gardi, vipin.kumar, shiraz.hashim, amit.virdi, vipulkumar.samar, viresh.linux, salvatore.dedominicis, deepak.sikri, lrg, vincenzo.frascino [-- Attachment #1.1: Type: text/plain, Size: 595 bytes --] On Fri, Feb 24, 2012 at 04:25:49PM +0530, Viresh Kumar wrote: > SET_SYSTEM_SLEEP_PM_OPS writes .poweroff = *_resume once. Then we overwrite it > again explicitly as .poweroff = snd_soc_poweroff. Even though it works, as the Applied but please do try to use subject lines appropriate for the subsystem you're submitting against. I'd also suggest creating a mailing list for ST internal people if you need to CC so many people on your team, the vger lists have a fairly low limit on the number of CCs they will accept which I think is about twenty or so, you're using a fair proportion of that. [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] sound/soc-core: Don't overwrite .poweroff in snd_soc_pm_ops 2012-02-24 14:46 ` [PATCH] sound/soc-core: Don't overwrite .poweroff in snd_soc_pm_ops Mark Brown @ 2012-02-24 14:57 ` viresh kumar 2012-02-24 14:59 ` Mark Brown 0 siblings, 1 reply; 3+ messages in thread From: viresh kumar @ 2012-02-24 14:57 UTC (permalink / raw) To: Mark Brown Cc: pratyush.anand, Viresh Kumar, rajeev-dlh.kumar, bhavna.yadav, bhupesh.sharma, armando.visconti, alsa-devel, vipin.kumar, shiraz.hashim, amit.virdi, mirko.gardi, salvatore.dedominicis, deepak.sikri, vipulkumar.samar, lrg, vincenzo.frascino On Feb 24, 2012 8:16 PM, "Mark Brown" <broonie@opensource.wolfsonmicro.com> wrote: > > Applied but please do try to use subject lines appropriate for the > subsystem you're submitting against. I'd also suggest creating a > mailing list for ST internal people if you need to CC so many people on > your team, the vger lists have a fairly low limit on the number of CCs > they will accept which I think is about twenty or so, you're using a > fair proportion of that. What's the preferred heading for sound/soc? We do have an internal list but we can't get mails from non st id's on that. I will check other ways to do it. -- Viresh ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] sound/soc-core: Don't overwrite .poweroff in snd_soc_pm_ops 2012-02-24 14:57 ` viresh kumar @ 2012-02-24 14:59 ` Mark Brown 0 siblings, 0 replies; 3+ messages in thread From: Mark Brown @ 2012-02-24 14:59 UTC (permalink / raw) To: viresh kumar Cc: pratyush.anand, Viresh Kumar, rajeev-dlh.kumar, bhavna.yadav, bhupesh.sharma, armando.visconti, alsa-devel, vipin.kumar, shiraz.hashim, amit.virdi, mirko.gardi, salvatore.dedominicis, deepak.sikri, vipulkumar.samar, lrg, vincenzo.frascino [-- Attachment #1.1: Type: text/plain, Size: 197 bytes --] On Fri, Feb 24, 2012 at 06:57:00AM -0800, viresh kumar wrote: > What's the preferred heading for sound/soc? ASoC, this is the sort of thing that is readily discoverable by looking at the logs... [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-02-24 14:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <a20a22fcfed7b4e62069ef8abebfa89f557646c2.1330080832.git.viresh.kumar@st.com>
2012-02-24 14:46 ` [PATCH] sound/soc-core: Don't overwrite .poweroff in snd_soc_pm_ops Mark Brown
2012-02-24 14:57 ` viresh kumar
2012-02-24 14:59 ` Mark Brown
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.