linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [next-rc] Compile Error fs/btrfs/diskio.c
Date: Mon, 29 Nov 2010 10:41:27 -0500	[thread overview]
Message-ID: <1291045244-sup-6390@think> (raw)
In-Reply-To: <AANLkTi=GVdSTacEVPRqQJu0Fktm8H4aDYfF5wuDDnrH4@mail.gmail.com>

Excerpts from Mitch Harder's message of 2010-11-27 17:53:23 -0500:
> I've been getting a compile error when building the 'next-rc' branch
> of btrfs-unstable.
>=20
>   CC      fs/btrfs/disk-io.o
> fs/btrfs/disk-io.c: In function =E2=80=98btree_migratepage=E2=80=99:
> fs/btrfs/disk-io.c:716: error: called object =E2=80=980u=E2=80=99 is =
not a function
> make[2]: *** [fs/btrfs/disk-io.o] Error 1
> make[1]: *** [fs/btrfs] Error 2
> make: *** [fs] Error 2
>=20
> Line 716 of fs/btrfs/disk-io.c is:
>=20
>         return migrate_page(mapping, newpage, page);
>=20
> This is related to the "Btrfs: add migrate page for metadata inode"
> patch (the first patch in the set of patches added to the next-rc
> branch).

I've pushed out a similar fix in the next-rc branch and the master
branch.  Waiting on korg mirrors to update before I send the pull
request.

Thanks!

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-11-29 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 22:53 [next-rc] Compile Error fs/btrfs/diskio.c Mitch Harder
2010-11-29 15:41 ` Chris Mason [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=1291045244-sup-6390@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mitch.harder@sabayonlinux.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).