public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ryusuke Konishi" <konishi.ryusuke@lab.ntt.co.jp>
To: "Chris Mason" <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix build errors of extent_io.c
Date: Tue, 6 Jan 2009 02:29:17 +0900	[thread overview]
Message-ID: <c4a7c9420901050929q37f4b640wdebad72fe227e456@mail.gmail.com> (raw)
In-Reply-To: <1231170459.4290.90.camel@think.oraclecorp.com>

2009/1/6 Chris Mason <chris.mason@oracle.com>:
> On Wed, 2008-12-24 at 17:56 +0900, Ryusuke Konishi wrote:
>> Hi Chris,
>>
>> I've started to read and try btrfs, and soon met the following build
>> errors.  The attached patch fixes the problem.
>>
>> Could you check this?
>>
>
> Strange, I wonder why your gcc complains and mine doesn't ;)  I'll fix
> these up thouhg.

Because I tried it on a powerpc ;)
The check of EXPORT_SYMBOL macros seems to be more strict
than that of x86.

As you can tell, my intention was to test endian problems,
and, so far, btrfs is perfectly working on both architectures
(except I met a freeze due to a disk full).
I mean the compatibilty of disk image was achieved between
x86 and ppc64 without problems.

Ryusuke

  reply	other threads:[~2009-01-05 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-24  8:56 [PATCH] Btrfs: fix build errors of extent_io.c Ryusuke Konishi
2009-01-05 15:47 ` Chris Mason
2009-01-05 17:29   ` Ryusuke Konishi [this message]
2009-01-05 17:37     ` Christoph Hellwig
2009-01-05 17:39       ` Chris Mason
2009-01-05 17:48         ` Ryusuke Konishi

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=c4a7c9420901050929q37f4b640wdebad72fe227e456@mail.gmail.com \
    --to=konishi.ryusuke@lab.ntt.co.jp \
    --cc=chris.mason@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox