All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Mark WM8350 mask revision as readable to match silicon
Date: Sun, 3 May 2009 23:04:22 +0100	[thread overview]
Message-ID: <20090503220420.GA22353@sirena.org.uk> (raw)
In-Reply-To: <20090503215728.GC3278@sortiz.org>

On Sun, May 03, 2009 at 11:57:29PM +0200, Samuel Ortiz wrote:
> On Thu, Apr 30, 2009 at 02:44:29PM +0100, Mark Brown wrote:

> > No impact unless someone has written additional kernel code.

> All 3 patches applied to my for-next branch, thanks.

At least the patch for the caching of volatile registers really ought to
go into 2.6.30 if possible - not having it breaks the audio driver for
the chip.

  reply	other threads:[~2009-05-03 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 13:44 [PATCH] mfd: Mark WM8350 mask revision as readable to match silicon Mark Brown
2009-05-03 21:57 ` Samuel Ortiz
2009-05-03 22:04   ` Mark Brown [this message]
2009-05-04  7:50     ` Samuel Ortiz
  -- strict thread matches above, loose matches on Subject: below --
2009-04-22 20:46 Mark Brown
2009-03-12 10:17 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=20090503220420.GA22353@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.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.