From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Paul Gortmaker" <paul.gortmaker@windriver.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"\"Heiko Stübner\"" <heiko@sntech.de>,
"Liam Girdwood" <lrg@slimlogic.co.uk>
Subject: Re: linux-next: build failure after merge of the moduleh tree
Date: Tue, 11 Oct 2011 14:05:34 +0100 [thread overview]
Message-ID: <20111011130534.GA3471@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111011192515.1f69837816e4cebd1e097385@canb.auug.org.au>
On Tue, Oct 11, 2011 at 07:25:15PM +1100, Stephen Rothwell wrote:
> I have applied the following patch for today. Mark, Liam, this should be
> applied to the regulator tree.
I open coded this since it was easier than fishing the patch out of the
backtrace.
next prev parent reply other threads:[~2011-10-11 13:05 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 8:25 linux-next: build failure after merge of the moduleh tree Stephen Rothwell
2011-10-11 13:05 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-23 4:51 Stephen Rothwell
2012-03-23 12:49 ` Paul Gortmaker
2012-03-23 13:03 ` Stephen Rothwell
2011-11-01 7:38 Stephen Rothwell
2011-10-12 6:29 Stephen Rothwell
2011-10-11 8:39 Stephen Rothwell
2011-10-04 7:32 Stephen Rothwell
2011-10-04 7:21 Stephen Rothwell
2011-10-04 15:24 ` Jonathan Cameron
2011-10-04 7:11 Stephen Rothwell
2011-10-04 7:03 Stephen Rothwell
2011-10-04 7:35 ` Kalle Valo
2011-10-04 8:14 ` Stephen Rothwell
2011-10-04 15:09 ` Larry Finger
2011-09-30 4:50 Stephen Rothwell
2011-09-30 12:52 ` Linus Walleij
2011-09-30 13:19 ` Stephen Rothwell
2011-10-03 6:55 ` Linus Walleij
2011-09-30 18:56 ` Paul Gortmaker
2011-09-28 8:41 Stephen Rothwell
2011-09-28 13:42 ` Paul Gortmaker
2011-09-29 0:15 ` Paul Gortmaker
2011-09-29 1:15 ` Stephen Rothwell
2011-09-28 8:35 Stephen Rothwell
2011-09-28 16:42 ` Kalle Valo
2011-09-28 8:25 Stephen Rothwell
2011-09-28 8:18 Stephen Rothwell
2011-10-09 5:08 ` Paul Gortmaker
2011-10-09 18:01 ` Chris Ball
2011-09-28 8:00 Stephen Rothwell
2011-09-28 7:50 Stephen Rothwell
2011-09-28 7:42 Stephen Rothwell
2011-09-28 7:58 ` Borislav Petkov
2011-09-28 7:10 Stephen Rothwell
2011-08-23 5:08 Stephen Rothwell
2011-08-23 9:59 ` Felipe Balbi
2011-09-02 18:32 ` Geert Uytterhoeven
2011-09-05 10:39 ` Felipe Balbi
2011-08-10 1:49 Stephen Rothwell
2011-08-03 4:16 Stephen Rothwell
2011-08-03 14:26 ` Greg KH
2011-08-03 4:10 Stephen Rothwell
2011-08-02 5:13 Stephen Rothwell
2011-08-02 10:15 ` Alasdair G Kergon
2011-08-01 3:58 Stephen Rothwell
2011-07-29 7:09 Stephen Rothwell
2011-07-31 6:59 ` Paul Gortmaker
2011-07-29 7:06 Stephen Rothwell
2011-07-31 7:44 ` Paul Gortmaker
2011-08-01 0:30 ` Stephen Rothwell
2011-07-29 6:48 Stephen Rothwell
2011-07-31 7:30 ` Paul Gortmaker
2011-07-29 6:24 Stephen Rothwell
2011-07-31 7:26 ` Paul Gortmaker
2011-07-29 6:19 Stephen Rothwell
2011-07-31 8:08 ` Paul Gortmaker
2011-07-29 5:41 Stephen Rothwell
2011-07-29 5:30 Stephen Rothwell
2011-07-29 5:25 Stephen Rothwell
2011-07-29 5:37 ` Stephen Rothwell
2011-07-31 6:31 ` Paul Gortmaker
2011-07-31 8:14 ` Paul Gortmaker
2011-07-29 5:10 Stephen Rothwell
2011-07-30 19:03 ` Dmitry Torokhov
2011-07-29 5:10 Stephen Rothwell
2011-07-31 4:45 ` Paul Gortmaker
2011-07-29 4:56 Stephen Rothwell
2011-07-31 5:44 ` Paul Gortmaker
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=20111011130534.GA3471@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=paul.gortmaker@windriver.com \
--cc=sfr@canb.auug.org.au \
/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).