From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755609AbcBXOhX (ORCPT ); Wed, 24 Feb 2016 09:37:23 -0500 Received: from kanga.kvack.org ([205.233.56.17]:45662 "EHLO kanga.kvack.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750931AbcBXOhW (ORCPT ); Wed, 24 Feb 2016 09:37:22 -0500 Date: Wed, 24 Feb 2016 09:37:19 -0500 From: Benjamin LaHaise To: Sedat Dilek Cc: linux-next , LKML , Stephen Rothwell , linux-aio@kvack.org Subject: Re: linux-next: Tree for Feb 24 Message-ID: <20160224143719.GE7382@kvack.org> References: <20160224163414.260db0ec@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 24, 2016 at 07:32:17AM +0100, Sedat Dilek wrote: > On Wed, Feb 24, 2016 at 6:34 AM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20160223: > > > ... > > The aio tree still had a build failure so I used the version from > > next-20160111. > > > > Might be good to poke the maintainer as I am seeing this for a long > time in Linux-next. These are architecture code related build failures that arch maintainers need to fix. Avoiding pulling the tree allows people to ignore the issue, which isn't going to get things fixed. I provided an example how to implement the 64 bit __get_user() without generating warnings, and it is now up to maintainers to adapt it for their architecture. -ben > - Sedat - -- "Thought is the essence of where you are now."