All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Timur Tabi <timur@freescale.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ALSA: ASoc: Add regulator support to CS4270 codec driver
Date: Sun, 29 Nov 2009 01:44:33 +0100	[thread overview]
Message-ID: <20091129004433.GZ14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <4B11A19D.4070301@freescale.com>

On Sat, Nov 28, 2009 at 04:18:05PM -0600, Timur Tabi wrote:
> Mark Brown wrote:
> >The regulator header file handles that -it provides stub versions of the
> >core consumer API calls to save all the drivers having to have
> >conditional code in them.
> 
> Ok, that works for me.
> 
> However, when I tried to apply the patch to the for-2.6.33 branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git,
> it fails:
> 
> $ patch -p 1 <
> "/home/b04825/.mozilla/seamonkey/fl00b35q.default/Mail/Local
> Folders/patches"
> patching file sound/soc/codecs/cs4270.c
> Hunk #5 FAILED at 651.
> Hunk #6 succeeded at 673 (offset -7 lines).
> Hunk #8 succeeded at 779 (offset -7 lines).
> Hunk #9 succeeded at 895 (offset -16 lines).
> 1 out of 9 hunks FAILED -- saving rejects to file sound/soc/codecs/cs4270.c.rej
> 
> I'm on vacation until the end of the year, so I can't test this
> driver thoroughly, but I'd like to make sure it at least compiles
> and boots before I ack it.

It does compile and does boot, we're testing this already on mayn
devices and it works fine. However, there have been updates to that
driver due to changes in the suspend/resume paths.

Mark, can you resolve those conflicts easily or do you want me to do it?

Thanks,
Daniel

  reply	other threads:[~2009-11-29  0:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 14:36 [PATCH] ALSA: ASoc: Add regulator support to CS4270 codec driver Daniel Mack
2009-11-25 15:01 ` Mark Brown
2009-11-25 15:20   ` Daniel Mack
2009-11-25 15:38     ` Mark Brown
2009-11-25 15:46       ` Daniel Mack
2009-11-26 15:48       ` Daniel Mack
2009-11-26 16:03         ` Mark Brown
2009-11-26 17:42           ` Daniel Mack
2009-11-27 11:25             ` Mark Brown
2009-11-27 12:41               ` Daniel Mack
2009-11-27 13:32                 ` Mark Brown
2009-11-28 20:23                   ` Timur Tabi
2009-11-28 20:31                     ` Mark Brown
2009-11-28 22:18                       ` Timur Tabi
2009-11-29  0:44                         ` Daniel Mack [this message]
2009-11-29  4:34                           ` Timur Tabi
2009-11-29  8:35                             ` Daniel Mack
2009-11-30 10:12                               ` Daniel Mack
     [not found]                           ` <5610599F537DD74A8D1F5CC946A7507303478C40@az33exm25.fsl.freescale.net>
2009-11-30 12:01                             ` Mark Brown
2009-11-30 12:36                               ` Daniel Mack
2009-11-30 15:57                                 ` Daniel Mack
2009-11-30 16:12                                   ` Mark Brown
2009-11-30 16:51                                     ` Daniel Mack
2009-11-30 16:56                                       ` Daniel Mack
2009-12-04 12:00                                         ` Daniel Mack
2009-12-04 12:07                                           ` Mark Brown
2009-12-05  2:54                                             ` Timur Tabi
2009-12-05  3:51                                               ` Mark Brown
2009-12-05 17:03                                         ` Timur Tabi
2009-12-07 13:16                                           ` 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=20091129004433.GZ14091@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=timur@freescale.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.