From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752874Ab1HIPB7 (ORCPT ); Tue, 9 Aug 2011 11:01:59 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:36406 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752035Ab1HIPB5 (ORCPT ); Tue, 9 Aug 2011 11:01:57 -0400 Date: Wed, 10 Aug 2011 00:01:53 +0900 From: Mark Brown To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build warnings after merge of the regmap tree Message-ID: <20110809150152.GD15861@opensource.wolfsonmicro.com> References: <20110809132111.af88776afc00f9e87e1bd6a1@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110809132111.af88776afc00f9e87e1bd6a1@canb.auug.org.au> X-Cookie: Be careful! UGLY strikes 9 out of 10! User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 09, 2011 at 01:21:11PM +1000, Stephen Rothwell wrote: > After merging the regmap tree, today's linux-next build (x86_64 > allmodconfig) produced these warning: Well, if you will go and test with minority architectures with strange choices for standard types :) Should be fixed in -next tomorrow.