From: Mark Brown <broonie@opensource•wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for December 27
Date: Mon, 27 Dec 2010 11:38:58 +0000 [thread overview]
Message-ID: <20101227113857.GA31293@sirena.org.uk> (raw)
In-Reply-To: <20101227170451.a9a9f873.sfr@canb.auug.org.au>
On Mon, Dec 27, 2010 at 05:04:51PM +1100, Stephen Rothwell wrote:
> The sound-asoc tree also had a build failure, so I used the version from
> next-20101221.
What is the problem you are seeing in the sound-asoc tree? I saw a mail
about the sound tree but didn't see any failures reported for ASoC.
next prev parent reply other threads:[~2010-12-27 11:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 6:04 linux-next: Tree for December 27 Stephen Rothwell
2010-12-27 8:04 ` Sedat Dilek
2010-12-27 9:11 ` Stephen Rothwell
2010-12-27 9:55 ` Sedat Dilek
2010-12-27 12:09 ` Sedat Dilek
2010-12-27 11:38 ` Mark Brown [this message]
2010-12-27 15:20 ` Stephen Rothwell
2010-12-27 15:38 ` Mark Brown
2010-12-27 14:36 ` Piotr Hosowicz
2010-12-27 14:48 ` Sedat Dilek
2010-12-27 14:57 ` Piotr Hosowicz
2010-12-27 15:08 ` Sedat Dilek
2010-12-27 15:13 ` Piotr Hosowicz
2010-12-27 15:45 ` Piotr Hosowicz
2010-12-27 16:16 ` Sedat Dilek
2010-12-28 14:27 ` Piotr Hosowicz
2010-12-28 15:09 ` Piotr Hosowicz
2010-12-27 19:21 ` linux-next: Tree for December 27 (drivers/target/) Randy Dunlap
2010-12-27 22:47 ` Nicholas A. Bellinger
2010-12-27 19:55 ` [PATCH -next] ocfs2: fix build for OCFS2_FS_STATS not enabled Randy Dunlap
2010-12-27 20:52 ` Joel Becker
2010-12-27 21:41 ` Randy Dunlap
2010-12-27 19:57 ` linux-next: Tree for December 27 (drivers/target) Randy Dunlap
2010-12-27 22:49 ` Nicholas A. Bellinger
2010-12-28 15:08 ` James Bottomley
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=20101227113857.GA31293@sirena.org.uk \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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