From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-SH <linux-sh@vger.kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] fbdev: sh_mobile_hdmi: fixup compile error
Date: Wed, 29 Dec 2010 13:33:34 +0000 [thread overview]
Message-ID: <9668ee76-6e43-43d5-a641-e0db2d4376d1@email.android.com> (raw)
In-Reply-To: <20101229062555.GA12369@linux-sh.org> (sfid-20101229_062749_985456_BD4C209A)
Applied, thanks. (Sorry about top posting, using my phone).
"Paul Mundt" <lethal@linux-sh.org> wrote:
>On Tue, Dec 28, 2010 at 03:06:46PM +0000, Mark Brown wrote:
>> On Mon, Dec 27, 2010 at 01:42:20PM +0900, Kuninori Morimoto wrote:
>> > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>> > ---
>> > >> Paul
>> >
>> > This patch is not needed for now on Paul's tree.
>> > But seems to be needed after ALSA tree merge.
>> >
>> > >> Mark, Liam
>> >
>> > this patch is needed on current Mark's "for-2.6.38" tree.
>>
>> Paul, do you want to apply this or shall I?
>
>It doesn't really matter to me, but since it seems to depend on your
>merge perhaps it makes more sense to merge through the ALSA tree,
>simply
>in terms of limiting bisect damage.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
prev parent reply other threads:[~2010-12-29 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 4:42 [PATCH] fbdev: sh_mobile_hdmi: fixup compile error Kuninori Morimoto
2010-12-28 15:06 ` Mark Brown
2010-12-29 6:25 ` Paul Mundt
2010-12-29 13:33 ` Mark Brown [this message]
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=9668ee76-6e43-43d5-a641-e0db2d4376d1@email.android.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox