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 Dec 19
Date: Tue, 20 Dec 2011 11:54:39 +0000 [thread overview]
Message-ID: <20111220115439.GM2866@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111220142048.eeccb51ed290d8223ba2c580@canb.auug.org.au>
On Tue, Dec 20, 2011 at 02:20:48PM +1100, Stephen Rothwell wrote:
> Which I reported to you on Dec 15 (along with another build error in the
> regulator tree that you have fixed). You even created a patch to fix it
> (Subject: [PATCH] mfd: Declare da9052_regmap_config for the bus drivers)
> but that has not appeared in your tree yet.
Pushed now, I had obviously thought the patch was pushed into my tree
and obviously everything was working locally.
next prev parent reply other threads:[~2011-12-20 11:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 7:55 linux-next: Tree for Dec 19 Stephen Rothwell
2011-12-19 20:32 ` linux-next: Tree for Dec 19 (xen) Randy Dunlap
2011-12-19 20:32 ` Randy Dunlap
2011-12-19 20:47 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-12-19 20:38 ` linux-next: Tree for Dec 19 (staging/media/go7007) Randy Dunlap
2011-12-19 20:44 ` linux-next: Tree for Dec 19 (nfc) Randy Dunlap
2011-12-20 16:39 ` Samuel Ortiz
2011-12-20 20:14 ` Randy Dunlap
2011-12-20 20:14 ` Randy Dunlap
2011-12-21 19:57 ` Randy Dunlap
2011-12-21 19:57 ` Randy Dunlap
2011-12-21 19:02 ` John W. Linville
2011-12-21 20:20 ` Randy Dunlap
[not found] ` <4EF23A1F.60803-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-12-21 20:42 ` Samuel Ortiz
2011-12-21 20:42 ` Samuel Ortiz
2011-12-21 21:58 ` Randy Dunlap
2011-12-21 23:35 ` Samuel Ortiz
2011-12-22 1:52 ` Randy Dunlap
2011-12-22 1:03 ` Stephen Rothwell
2011-12-20 1:52 ` linux-next: Tree for Dec 19 Mark Brown
2011-12-20 3:20 ` Stephen Rothwell
2011-12-20 6:39 ` Stephen Rothwell
2011-12-20 11:54 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-19 3:26 Stephen Rothwell
2012-12-19 3:26 ` Stephen Rothwell
2013-12-19 5:51 Stephen Rothwell
2013-12-19 5:51 ` Stephen Rothwell
2014-12-19 8:47 Stephen Rothwell
2016-12-19 2:38 Stephen Rothwell
2017-12-19 5:43 Stephen Rothwell
2018-12-19 7:45 Stephen Rothwell
2019-12-19 7:11 Stephen Rothwell
2022-12-19 0:56 Stephen Rothwell
2023-12-19 4:41 Stephen Rothwell
2024-12-19 6:37 Stephen Rothwell
2025-12-19 3:14 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=20111220115439.GM2866@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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.