From: David Sterba <dave@jikos.cz>
To: Wade Cline <clinew@linux.vnet.ibm.com>
Cc: linux-btrfs@vger.kernel.org, cmm@linux.vnet.ibm.com
Subject: Re: [RFC][PATCH] Btrfs-progs: Fix compiler warnings on PPC64.
Date: Thu, 20 Sep 2012 16:15:04 +0200 [thread overview]
Message-ID: <20120920141504.GP17430@twin.jikos.cz> (raw)
In-Reply-To: <505365A9.2080900@linux.vnet.ibm.com>
On Fri, Sep 14, 2012 at 10:13:13AM -0700, Wade Cline wrote:
> By the time kerncompat.h is included, u64 is almost always defined to
> the non-compatible value. So either kerncompat.h needs to be defined as the
> -first-
This makes most sense to me.
Although the include files should go in the order 1. system 2. local,
and kernecompat.h is local, it's special in it's own way and i don't see
any problem with that.
david
prev parent reply other threads:[~2012-09-20 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 23:21 [RFC][PATCH] Btrfs-progs: Fix compiler warnings on PPC64 clinew
2012-09-14 13:59 ` David Sterba
2012-09-14 17:13 ` Wade Cline
2012-09-20 14:15 ` David Sterba [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=20120920141504.GP17430@twin.jikos.cz \
--to=dave@jikos.cz \
--cc=clinew@linux.vnet.ibm.com \
--cc=cmm@linux.vnet.ibm.com \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.