From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, Liam Girdwood <lrg@slimlogic.co.uk>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: sh: fix migor.c compilation
Date: Wed, 9 May 2012 12:17:02 +0100 [thread overview]
Message-ID: <20120509111701.GI3955@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1205091255190.8599@axis700.grange>
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
On Wed, May 09, 2012 at 12:57:05PM +0200, Guennadi Liakhovetski wrote:
> Fix a recent compilation breakage, caused by a change in SH clock API.
How recent - when and where was the API changed?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-09 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 10:57 [PATCH] ASoC: sh: fix migor.c compilation Guennadi Liakhovetski
2012-05-09 11:17 ` Mark Brown [this message]
2012-05-09 11:35 ` Guennadi Liakhovetski
2012-05-09 11:37 ` 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=20120509111701.GI3955@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=g.liakhovetski@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).