From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754740AbdFWR7v (ORCPT ); Fri, 23 Jun 2017 13:59:51 -0400 Received: from mail-pg0-f42.google.com ([74.125.83.42]:33471 "EHLO mail-pg0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754645AbdFWR7t (ORCPT ); Fri, 23 Jun 2017 13:59:49 -0400 Date: Fri, 23 Jun 2017 10:59:46 -0700 From: Brian Norris To: =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: Stephen Rothwell , Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: build warning after merge of the l2-mtd tree Message-ID: <20170623175946.GA56401@google.com> References: <20170623113206.29042011@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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 Fri, Jun 23, 2017 at 06:56:53AM +0200, Rafał Miłecki wrote: > On 2017-06-23 03:32, Stephen Rothwell wrote: > >After merging the l2-mtd tree, today's linux-next build (x86_64 > >allmodconfig) produced this warning: > > This code has been just moved, so the warning was already there before. > > But it's of course a good opportunity to fix it :) We now allow it to build with COMPILE_TEST, which means it can show up on 64-bit architectures, where sizeof(size_t) != sizeof(int). I failed to add it to my local 64-bit build tests, so I didn't notice this. But fixed now. Brian