All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	alsa-devel@alsa-project.org, Nicolas Pitre <nico@fluxnic.net>,
	linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
	Arnaud Patard <arnaud.patard@rtp-net.org>
Subject: Re: [PATCH v2] ASoC: Fix build error in sound/soc/kirkwood/kirkwood-i2s.c
Date: Wed, 28 Dec 2011 11:37:46 +0000	[thread overview]
Message-ID: <20111228113745.GD24405@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1325059522.18468.4.camel@phoenix>

On Wed, Dec 28, 2011 at 04:05:22PM +0800, Axel Lin wrote:
> Since commit db33f4de "ARM: Orion: Remove address map info from all platform data structures",
> the dram is removed from struct kirkwood_asoc_platform_data.

Applied, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Arnaud Patard <arnaud.patard@rtp-net.org>,
	Andrew Lunn <andrew@lunn.ch>, Nicolas Pitre <nico@fluxnic.net>,
	Liam Girdwood <lrg@ti.com>,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] ASoC: Fix build error in sound/soc/kirkwood/kirkwood-i2s.c
Date: Wed, 28 Dec 2011 11:37:46 +0000	[thread overview]
Message-ID: <20111228113745.GD24405@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1325059522.18468.4.camel@phoenix>

On Wed, Dec 28, 2011 at 04:05:22PM +0800, Axel Lin wrote:
> Since commit db33f4de "ARM: Orion: Remove address map info from all platform data structures",
> the dram is removed from struct kirkwood_asoc_platform_data.

Applied, thanks.

  reply	other threads:[~2011-12-28 11:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  8:05 [PATCH v2] ASoC: Fix build error in sound/soc/kirkwood/kirkwood-i2s.c Axel Lin
2011-12-28  8:05 ` Axel Lin
2011-12-28 11:37 ` Mark Brown [this message]
2011-12-28 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=20111228113745.GD24405@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=andrew@lunn.ch \
    --cc=arnaud.patard@rtp-net.org \
    --cc=axel.lin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=nico@fluxnic.net \
    /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.