From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754139Ab1LTBwl (ORCPT ); Mon, 19 Dec 2011 20:52:41 -0500 Received: from cassiel.sirena.org.uk ([80.68.93.111]:50855 "EHLO cassiel.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753203Ab1LTBwi (ORCPT ); Mon, 19 Dec 2011 20:52:38 -0500 Date: Tue, 20 Dec 2011 01:52:35 +0000 From: Mark Brown To: Stephen Rothwell Cc: linux-next@vger.kernel.org, LKML Subject: Re: linux-next: Tree for Dec 19 Message-ID: <20111220015235.GB8290@sirena.org.uk> References: <20111219185556.f07c1f43e28cfd594aaa5fe0@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111219185556.f07c1f43e28cfd594aaa5fe0@canb.auug.org.au> X-Cookie: tax office, n.: User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: broonie@sirena.org.uk X-SA-Exim-Scanned: No (on cassiel.sirena.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.