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 01:52:35 +0000 [thread overview]
Message-ID: <20111220015235.GB8290@sirena.org.uk> (raw)
In-Reply-To: <20111219185556.f07c1f43e28cfd594aaa5fe0@canb.auug.org.au>
On Mon, Dec 19, 2011 at 06:55:56PM +1100, Stephen Rothwell wrote:
> The regmap tree still has one build failure so I used the version of the
> tree from next-20111214.
Please tell maintainers if you're doing this. What is the issue here?
The only thing I can think of is the broken GPIO driver that got merged
some time ago without its dependencies which you were (much more sanely)
flagging as broken.
next prev parent reply other threads:[~2011-12-20 1:52 UTC|newest]
Thread overview: 30+ 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: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-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 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 ` Mark Brown [this message]
2011-12-20 3:20 ` linux-next: Tree for Dec 19 Stephen Rothwell
2011-12-20 6:39 ` Stephen Rothwell
2011-12-20 11:54 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2012-12-19 3:26 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=20111220015235.GB8290@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