From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: sound tree build warning
Date: Mon, 10 Aug 2009 19:43:32 +0100 [thread overview]
Message-ID: <20090810184331.GD24947@sirena.org.uk> (raw)
In-Reply-To: <s5hws5cm89y.wl%tiwai@suse.de>
On Mon, Aug 10, 2009 at 09:34:49AM +0200, Takashi Iwai wrote:
> Looks like a forgotten piece since the reg-cache branch merge.
> Mark, could you clean up?
The changes I pushed earlier today did so.
next prev parent reply other threads:[~2009-08-10 18:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 4:15 linux-next: sound tree build warning Stephen Rothwell
2009-08-10 7:34 ` Takashi Iwai
2009-08-10 18:43 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-12 1:13 Stephen Rothwell
2009-08-12 5:58 ` Takashi Iwai
2009-08-12 13:33 ` Mark Brown
2009-08-11 3:22 Stephen Rothwell
2009-08-11 6:17 ` Takashi Iwai
2009-08-11 6:21 ` Stephen Rothwell
2009-07-15 3:13 Stephen Rothwell
2009-07-15 8:35 ` Mark Brown
2009-07-15 9:09 ` Takashi Iwai
2009-07-15 9:12 ` Mark Brown
2009-07-08 4:18 Stephen Rothwell
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=20090810184331.GD24947@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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