From: Theodore Tso <tytso@mit.edu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ext4,jbd2 - tracepoints: fix format string compile warnings (ino_t)
Date: Sat, 5 Sep 2009 09:41:20 -0400 [thread overview]
Message-ID: <20090905134120.GH16217@mit.edu> (raw)
In-Reply-To: <20090903155619.GC26842@osiris.boeblingen.de.ibm.com>
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
prev parent reply other threads:[~2009-09-05 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 15:56 [PATCH] ext4,jbd2 - tracepoints: fix format string compile warnings (ino_t) Heiko Carstens
2009-09-05 13:41 ` Theodore Tso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090905134120.GH16217@mit.edu \
--to=tytso@mit.edu \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).