From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>,
"Balbi, Felipe" <balbi@ti.com>,
Liam@alsa-project.org, Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RESEND][PATCH] ASoC: Update omap/ams-delta for TTY API change
Date: Fri, 13 May 2011 10:25:32 +0100 [thread overview]
Message-ID: <4DCCF90C.7030301@ti.com> (raw)
In-Reply-To: <20110513070040.GA18783@opensource.wolfsonmicro.com>
On 13/05/11 08:00, Mark Brown wrote:
> On Fri, May 13, 2011 at 12:36:07AM +0200, Janusz Krzysztofik wrote:
>> Following the receive_buf() change to return the number of bytes
>> received, the cx20442 CODEC driver was updated to report that we
>> accepted all the data that was offered to us. Do the same with the
>> corresponding Amstrad Delta sound card level wrapper function, which is
>> actually registered as the tty line discipline callback instead of the
>> the CODEC function, which it then calls.
>>
>> Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
> but as the TTY API change is in the TTY tree at the minute and not ASoC
> you should send this to Greg K-H (ideally also with Liam's ack) unless
> it's not been applied by the time the merge window comes round.
Fine by me too.
Acked-by: Liam Girdwood <lrg@ti.com>
next prev parent reply other threads:[~2011-05-13 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 17:29 [PATCH] ASoC: Update omap/ams-delta for TTY API change Janusz Krzysztofik
2011-05-12 22:36 ` [RESEND][PATCH] " Janusz Krzysztofik
2011-05-13 7:00 ` Mark Brown
2011-05-13 9:25 ` Liam Girdwood [this message]
2011-06-03 21:37 ` Janusz Krzysztofik
2011-06-06 9:53 ` Liam Girdwood
2011-06-06 9:58 ` Felipe Balbi
2011-06-06 10:37 ` Janusz Krzysztofik
2011-06-06 10:31 ` Mark Brown
2011-06-06 10:46 ` Janusz Krzysztofik
2011-06-06 10:57 ` 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=4DCCF90C.7030301@ti.com \
--to=lrg@ti.com \
--cc=Liam@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=balbi@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=lrg@slimlogic.co.uk \
--cc=patches@opensource.wolfsonmicro.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.