From: Paul Mundt <lethal@linux-sh.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Kuninori Morimoto <morimoto.kuninori@renesas.com>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 4/4] sh: add FSI driver support for ms7724se
Date: Fri, 21 Aug 2009 08:43:27 +0900 [thread overview]
Message-ID: <20090820234327.GA31542@linux-sh.org> (raw)
In-Reply-To: <20090820190626.GH5032@sirena.org.uk>
On Thu, Aug 20, 2009 at 08:06:26PM +0100, Mark Brown wrote:
> On Thu, Aug 20, 2009 at 09:01:27PM +0900, Kuninori Morimoto wrote:
> > Signed-off-by: Kuninori Morimoto <morimoto.kuninori@renesas.com>
>
> > o become independent patch
>
> It looks like this should have another change to register the CODEC as
> an I2C device? Other than that it's fine from an ASoC point of view -
> is it OK to merge via ASoC due to the dependency on the platform data
> for the FSI?
I have other ms7724se patches queued up for 2.6.32, so the easiest thing
to do is just to leave this patch until the dependencies are upstream,
then I'll fold it in. This is how we usually handle these sorts of merge
dependencies anyways.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Kuninori Morimoto <morimoto.kuninori@renesas.com>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH v2 4/4] sh: add FSI driver support for ms7724se
Date: Thu, 20 Aug 2009 23:43:27 +0000 [thread overview]
Message-ID: <20090820234327.GA31542@linux-sh.org> (raw)
In-Reply-To: <20090820190626.GH5032@sirena.org.uk>
On Thu, Aug 20, 2009 at 08:06:26PM +0100, Mark Brown wrote:
> On Thu, Aug 20, 2009 at 09:01:27PM +0900, Kuninori Morimoto wrote:
> > Signed-off-by: Kuninori Morimoto <morimoto.kuninori@renesas.com>
>
> > o become independent patch
>
> It looks like this should have another change to register the CODEC as
> an I2C device? Other than that it's fine from an ASoC point of view -
> is it OK to merge via ASoC due to the dependency on the platform data
> for the FSI?
I have other ms7724se patches queued up for 2.6.32, so the easiest thing
to do is just to leave this patch until the dependencies are upstream,
then I'll fold it in. This is how we usually handle these sorts of merge
dependencies anyways.
next prev parent reply other threads:[~2009-08-20 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 12:01 [PATCH v2 4/4] sh: add FSI driver support for ms7724se Kuninori Morimoto
2009-08-20 12:01 ` Kuninori Morimoto
2009-08-20 19:06 ` Mark Brown
2009-08-20 19:06 ` [alsa-devel] [PATCH v2 4/4] sh: add FSI driver support for Mark Brown
2009-08-20 23:43 ` Paul Mundt [this message]
2009-08-20 23:43 ` [alsa-devel] [PATCH v2 4/4] sh: add FSI driver support for ms7724se Paul Mundt
2009-08-21 1:09 ` Kuninori Morimoto
2009-08-21 1:09 ` [alsa-devel] " Kuninori Morimoto
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=20090820234327.GA31542@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=morimoto.kuninori@renesas.com \
--cc=tiwai@suse.de \
/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.