From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: [PATCH] ext4,jbd2 - tracepoints: fix format string compile warnings (ino_t) Date: Sat, 5 Sep 2009 09:41:20 -0400 Message-ID: <20090905134120.GH16217@mit.edu> References: <20090903155619.GC26842@osiris.boeblingen.de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org To: Heiko Carstens Return-path: Received: from THUNK.ORG ([69.25.196.29]:49087 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751482AbZIENlV (ORCPT ); Sat, 5 Sep 2009 09:41:21 -0400 Content-Disposition: inline In-Reply-To: <20090903155619.GC26842@osiris.boeblingen.de.ibm.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Sep 03, 2009 at 05:56:19PM +0200, Heiko Carstens wrote: > Unlike on most other architectures ino_t is an unsigned int on s390. > So add an explicit cast to avoid lots of compile warnings: Added to the ext4 patch queue, thanks. In the future, I'd appreciate it if patches to ext4 could get cc'ed to linux-ext4@vger.kernel.org instead of linux-fsdevel@vger.kernel.org. That way they will get tracked using the patchwork system (at URL http://patchwork.ozlabs.org/project/linux-ext4) and it makes it less likely that the patch gets overlooked. - Ted