All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: dp@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
	lrg@slimlogic.co.uk
Subject: Re: [PATCH] ASoC: cs4270: fix dynamic initialization of register cache
Date: Thu, 6 Jan 2011 16:07:23 -0600	[thread overview]
Message-ID: <4D263D1B.7040506@freescale.com> (raw)
In-Reply-To: <20110106220406.GI8018@opensource.wolfsonmicro.com>

Mark Brown wrote:
> That'd be Liam in the multi-component conversion, though obviously that
> didn't cause any immediate issues.  The shared I/O code has been present
> since mid 2009 though, including the cache management.  This kind of
> comes back to what I'm saying about making your code as idiomatic as
> possible, the more a given piece of code diverges from standard idioms
> the more likely it is that it will be unintentially broken by some other
> change.

My code *was* idiomatic the last time I touched it, which was early 2009.

> FWIW using the standard stuff should just be a case providing defaults,
> calling snd_soc_set_cache_io() and removing your custom I/O functions.

Ok, I'll take a look at it tomorrow.

You'd think the guys at Crystal Semi would at least give me a free coffee mug or
something.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2011-01-06 22:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 18:52 [PATCH] ASoC: cs4270: fix dynamic initialization of register cache Timur Tabi
2011-01-06 20:15 ` Mark Brown
2011-01-06 20:24   ` Timur Tabi
2011-01-06 21:41     ` Mark Brown
2011-01-06 20:50   ` Timur Tabi
2011-01-06 21:31     ` Mark Brown
2011-01-06 21:35       ` Timur Tabi
2011-01-06 22:04         ` Mark Brown
2011-01-06 22:07           ` Timur Tabi [this message]
2011-01-06 22:31             ` 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=4D263D1B.7040506@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    /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.